>>> Unpacking source... >>> Unpacking epiphany-2.20.1.tar.bz2 to /var/tmp/portage/www-client/epiphany-2.20.1/work * Fixing OMF Makefiles ... [ ok ] * Running elibtoolize in: epiphany-2.20.1 * Applying portage-1.5.10.patch ... * Applying sed-1.5.6.patch ... >>> Source unpacked. >>> Compiling source in /var/tmp/portage/www-client/epiphany-2.20.1/work/epiphany-2.20.1 ... * econf: updating epiphany-2.20.1/config.sub with /usr/share/gnuconfig/config.sub * econf: updating epiphany-2.20.1/config.guess with /usr/share/gnuconfig/config.guess ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-scrollkeeper --with-engine=mozilla --enable-spell-checker --enable-python --with-gecko=firefox --enable-gtk-doc --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu [...] checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... configure: error: This program needs a gtk 2 gecko build
Created attachment 137422 [details] 'emerge --info' output
Created attachment 137423 [details] build log
Created attachment 137425 [details] config log
Which versions of mozilla-firefox{,-bin} do you have? The log says it's going to use gtkmozembed from firefox. Try running this command and here's the output on my system : $ pkg-config --libs firefox-gtkmozembed -Wl,-R/usr/lib/mozilla-firefox -Wl,-R/usr/lib/nspr -L/usr/lib/mozilla-firefox -L/usr/lib/nspr -lgtkembedmoz -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl
(In reply to comment #4) > Which versions of mozilla-firefox{,-bin} do you have? # eix -c mozilla-firefox [I] www-client/mozilla-firefox (2.0.0.10@11/30/2007): Firefox Web Browser [I] www-client/mozilla-firefox-bin (2.0.0.9@11/04/2007): Firefox Web Browser The log says it's going > to use gtkmozembed from firefox. Try running this command and here's the output > on my system : > > $ pkg-config --libs firefox-gtkmozembed > -Wl,-R/usr/lib/mozilla-firefox -Wl,-R/usr/lib/nspr -L/usr/lib/mozilla-firefox > -L/usr/lib/nspr -lgtkembedmoz -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl # pkg-config --libs firefox-gtkmozembed -Wl,-R/usr/lib64/nspr -Wl,-R/usr/lib64/mozilla-firefox -L/usr/lib64/nspr -L/usr/lib64/mozilla-firefox -lgtkembedmoz -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -ldl I had to add "/usr/bin" to PKG_CONFIG_PATH for the command to work (it's where nspr.pc is). Fixing this and exporting the envar has allowed me to compile epiphany. Where is PKG_CONFIG_PATH defined?
> Where is PKG_CONFIG_PATH defined? /etc/profile.{env,csh}
(In reply to comment #6) All /usr/lib/pkgconfig/mozilla-firefox-*.pc files installed by mozilla-firefox-2.0.0.10 require nspr >= 4.7.0 which is only available in a layman overlay. That version (4.7.0_pre20071016) installs nspr.pc in /usr/bin, so PKG_CONFIG_PATH must include "/usr/bin". I expect that downgrading to mozilla-firefox-2.0.0.9 (I am doing so now) will restore consistency and harmony to the universe, and then emerges of epiphany and yelp will complete normally.
PKG_CONFIG_PATH is not supposed to be defined for system packages. You only need to set it when you want to use libraries installed in other non-standard paths. Obviously, you're using an amd64 machine, but I only have an x86 for the moment. @mozilla herd, what do you guys think?
(In reply to comment #7) > All /usr/lib/pkgconfig/mozilla-firefox-*.pc files installed by > mozilla-firefox-2.0.0.10 require nspr >= 4.7.0 > What? Since when? And yes, that failure is due to the nspr ebuild being broken, but i already fixed it, reemerge. And we're talking about stuff in a overlay, so expect things like this.
(In reply to comment #9) > (In reply to comment #7) > > All /usr/lib/pkgconfig/mozilla-firefox-*.pc files installed by > > mozilla-firefox-2.0.0.10 require nspr >= 4.7.0 > > > > What? Since when? And yes, that failure is due to the nspr ebuild being broken, > but i already fixed it, reemerge. And we're talking about stuff in a overlay, > so expect things like this. > Well, that's what I found when I looked in the files /usr/lib/pkgconfig/mozilla-firefox-*.pc. I upgraded successfully to mozilla-firefox-2.0.0.11 which does not have the same issue so I am going to close this bug as FIXED.
