Closed Bug 890594 Opened 7 years ago Closed 7 years ago

No Linux x86_64 trunk builds newer than 2013-04-21 2.20a1 yet

Categories

(SeaMonkey :: Release Engineering, defect, major)

x86_64
Linux
defect
Not set
major

Tracking

(seamonkey2.20 affected, seamonkey2.21 affected, seamonkey2.22 affected, seamonkey2.23 affected)

RESOLVED WORKSFORME
Tracking Status
seamonkey2.20 --- affected
seamonkey2.21 --- affected
seamonkey2.22 --- affected
seamonkey2.23 --- affected

People

(Reporter: tonymec, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: 64bit)

No Linux x86_64 trunk builds newer than 2013-04-21 2.20a1. This can be ascertained by searching http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/?C=M;O=D for the string "linux-x86_64" or even "x-x" (both without quotes of course)

I'm sure the problem is known, but I thought I'd just open a bug so the progress (if any) can be followed.

In the mean time, some linux-i686 2.22 builds have been produced (until July 3rd at least) and they work on 64-bit Linux OSes even if they aren't what we 64-bit Linux users would prefer. Beware that they require 32-bit plugins (64-bit versions will be ignored) and 32-bit versions of Lightning and gdata-provider (if you enable a 64-bit version, all hell may break loose).
The issue, afaik, is because of failure to build.  

checking MOZ_DBUS_GLIB_LIBS... -L/lib64 -ldbus-glib-1 -ldbus-1 -lglib-2.0  
checking __attribute__ ((aligned ())) support... trying 64
64
checking for alsa... yes
checking MOZ_ALSA_CFLAGS... -I/usr/include/alsa  
checking MOZ_ALSA_LIBS... -lasound  
checking for gstreamer-0.10 >= 0.10.25
                      gstreamer-app-0.10
                      gstreamer-plugins-base-0.10... configure: error: gstreamer and gstreamer-plugins-base development packages are needed to build gstreamer backend. Install them or disable gstreamer support with --disable-gstreamer
------ config.log ------
configure:18040: checking _PANGOCHK_CFLAGS
configure:18045: checking _PANGOCHK_LIBS
configure:18125: checking for pango >= 1.14.0 pangoft2 >= 1.14.0 pangocairo >= 1.14.0
configure:18132: checking MOZ_PANGO_CFLAGS
configure:18137: checking MOZ_PANGO_LIBS
configure:18346: checking for gnome-vfs-2.0 >= 2.0 gnome-vfs-module-2.0 >= 2.0
configure:18353: checking MOZ_GNOMEVFS_CFLAGS
configure:18358: checking MOZ_GNOMEVFS_LIBS
configure:18693: checking for gconf-2.0 >= 1.2.1 gobject-2.0 
configure:18700: checking MOZ_GCONF_CFLAGS
configure:18705: checking MOZ_GCONF_LIBS
configure:19094: checking for dbus-1 >= 0.60
configure:19101: checking MOZ_DBUS_CFLAGS
configure:19106: checking MOZ_DBUS_LIBS
configure:19185: checking for dbus-glib-1 >= 0.60
configure:19192: checking MOZ_DBUS_GLIB_CFLAGS
configure:19197: checking MOZ_DBUS_GLIB_LIBS
configure:19660: checking __attribute__ ((aligned ())) support
configure:19677: /tools/gcc-4.5/bin/gcc -c -gdwarf-2 -DYUV_DISABLE_ASM=1 -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -pthread -Werror  conftest.c 1>&5
configure:20339: checking for alsa
configure:20346: checking MOZ_ALSA_CFLAGS
configure:20351: checking MOZ_ALSA_LIBS
configure:20581: checking for gstreamer-0.10 >= 0.10.25
                      gstreamer-app-0.10
                      gstreamer-plugins-base-0.10
configure: error: /builds/slave/c-cen-t-lnx64/build/mozilla/configure failed for mozilla
*** Fix above errors and then restart with               "make -f client.mk build"
make[1]: *** [configure] Error 1
make[1]: Leaving directory `/builds/slave/c-cen-t-lnx64/build'
make: *** [objdir/Makefile] Error 2
program finished with exit code 2
elapsedTime=12.881862
Bug 886180 - Disable gstreamer in SeaMonkey. r=KaiRo a=KaiRo for CLOSED TREE landing

The patch in:
https://hg.mozilla.org/comm-central/rev/9a6a19f66ed8
Missed out the Linux64 mozconfig(s)
Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23a1 ID:20130810003001 c-c:854f8af28f57 m-c:c5946a8bcd5b

Linux x86_64 nightlies are being built again. I thought I could VERIFY this bug but it hasn't even been marked FIXED… :-?
It seems the recent checkins for bug 886180 fixed this.
Setting WORKSFORME. Edmund, Philip, if I goofed (if it should remain open, or if another Resolution is more appropriate), feel free to change it.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.