I am having problems emerging seamonkey on a ppc powerbook. Here the last part of the failed emerge of seamonkey 1.0.1 [code] checking whether the compiler can resolve const ambiguities for templates... yeschecking whether the C++ "using" keyword can change access... yes checking whether the C++ "using" keyword resolves ambiguity... yes checking for "std::" namespace... yes checking whether standard template operator!=() is ambiguous... unambiguous checking for C++ reinterpret_cast... yes checking for C++ dynamic_cast to void*... yes checking whether C++ requires implementation of unused virtual methods... yes checking for trouble comparing to zero near std::operator!=()... no checking for LC_MESSAGES... yes checking for nspr-config... /usr/bin/nspr-config checking for NSPR - version >= 4.0.0 (skipping)... yes checking for nss-config... /usr/bin/nss-config checking for NSS - version >= 3.0.0 (skipping)... yes checking for jpeg_destroy_compress in -ljpeg... yes checking for gzread in -lz... yes checking for png_get_valid in -lpng... yes checking for pkg-config... /usr/bin/pkg-config checking for gtk+-2.0 >= 1.3.7... yes checking MOZ_GTK2_CFLAGS... -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking MOZ_GTK2_LIBS... -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 configure: error: --enable-application=APP is required [/code] [code] emerge --info Portage 2.0.54 (default-linux/ppc/2005.0, gcc-3.4.5, glibc-2.3.5-r3, 2.6.16-rc3 ppc) ================================================================= System uname: 2.6.16-rc3 ppc 7455, altivec supported Gentoo Base System version 1.6.14 ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2-r1 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-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CBUILD="powerpc-unknown-linux-gnu" CFLAGS="-O2 -mcpu=7450 -fno-strict-aliasing -mtune=G4 -maltivec -mabi=altivec -pipe" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=7450 -fno-strict-aliasing -mtune=G4 -maltivec -mabi=altivec -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy ccache distlocks sandbox sfperms strict userpriv usersandbox" [/code]
This would only be caused with a eclass in your portage overlay, I would check that you have no mozcoreconf.eclass in the overlay.
(In reply to comment #1) > This would only be caused with a eclass in your portage overlay, I would check > that you have no mozcoreconf.eclass in the overlay. > Yes there was a mozcoreconf.eclass in my portage overlay. Emerging Seamonkey seems to go without any errors now. So this was not a true bug? Sorry for the false alarm and thank you for the help.
