Hi, would it be possible to mark Firefox 1.5.0.7 at least ~alpha? It compiles and runs on my Alpha Personal Workstation 500au.
please post your emerge --info
As far as I can tell firefox-1.5.x.y doesn't compile correctly with gcc-3.4.6-rX (the resulting firefox binary just hangs and uses 100% CPU). gcc-4.1 and gcc-3.3 seem to work, but gcc-4.1 isn't keyworded yet and 3.3 is no longer current. Details on testing are available here: Bug #128777. Firefox-2.0_rc2 works when compiled with gcc-3.4.6-rX, so you may want to give that a try. It'll be unmasked onced firefox-2.0 is released. If you were able to get firefox-1.5.0.7 to compile correctly with gcc-3.4, please re-open this bug and post the output of `emerge --info`.
Emerge --info: ===== Start: ===== Portage 2.1-r2 (default-linux/alpha/2006.0, gcc-3.3.2, glibc-2.3.6-r4, 2.6.18-tfxtfx alpha) ================================================================= System uname: 2.6.18-tfxtfx alpha EV56 Gentoo Base System version 1.12.5 app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.2.11-r1 dev-lang/python: 2.3.5-r2, 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r4 ACCEPT_KEYWORDS="alpha" AUTOCLEAN="yes" CBUILD="alpha-unknown-linux-gnu" CFLAGS="-mcpu=ev56 -O2 -pipe" CHOST="alpha-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-mcpu=ev56 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer nostrip sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.be.gentoo.org/gentoo-portage" USE="alpha X alsa apache2 arts berkdb bitmap-fonts cli crypt cups debug dlloader dri eds encode esd foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 isdnlog jpeg kde libg++ libwww mad matrox mga mikmod motif mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre perl png pppd python qt qt3 quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev video_cards_matrox vorbis xml xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_mga video_cards_vga video_cards_fbdev" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS ===== :end ===== The thing is, it compiles, but after I start Firefox, X is constantly between 70 - 99% working... So it's not working completely...
(In reply to comment #2) > If you were able to get firefox-1.5.0.7 to compile correctly > with gcc-3.4, please re-open this bug and post the output of > `emerge --info`. (In reply to comment #3) > gcc-3.3.2 > ... > The thing is, it compiles, but after I start Firefox, X is constantly between > 70 - 99% working... So it's not working completely... To add ~alpha to firefox-1.5.0.7 we need the current ~alpha compiler (gcc-3.4.6-r2) to compile a working firefox binary. From all of our tests, it doesn't appear that firefox-1.5.0.7 and gcc-3.4.6-r2 are a winning combination. The source of the problem is not clear. Firefox and the whole alpha tool chain have very large code bases and since firefox doesn't segfault and there are no errors that stop compilation or firefox, finding the root cause is even more difficult. The good news is that Firefox 2.0 release candidates work fine when compiled with gcc-3.4.6-r2. Since firefox is moving to 2.0 soon, it isn't really worth it to try to fix this problem. If you want to try out the firefox 2.0 release candidate 3, just add the following to /etc/portage/package.unmask =www-client/mozilla-firefox-2.0_rc3
