The ebuild for www-client/mozilla-firefox-bin-2.0.0.14 does not check if pango is installed and compiled with USE="X" but the binary depends on libpangoxft-1.0.so.0. Reproducible: Always Steps to Reproduce: 1. install www-client/mozilla-firefox-bin-2.0.0.14 on a system without pango or pango installed with USE="-X" 2. start the binary Actual Results: /opt/firefox/firefox-bin: error while loading shared libraries: libpangoxft-1.0.so.0: cannot open shared object file: No such file or directory firefox-bin exited with non-zero status (127) Expected Results: - Dependency for x11-libs/pango - Check if Cairo was built with USE="X" (like in www-client/mozilla-firefox-2.0.0.14) - A running firefox
Fixed, thanks.
Not exactly, Mozilla still doesn't DEPEND on pango and it's not being pulled in. I am building from a clean environment within catalyst, livecd-stage1. The snapshot is from 20080629 and includes the "fix". It seems there is no choice but to depend on pango for it to be pulled in correctly.
Actually, the USE=X check is most probably the reason I was getting the following (cryptic) error (the "Unable to resolve x11-libs/pango to an installed package" part): >>> Emerging (5 of 147) www-client/mozilla-firefox-bin-2.0.0.14 to / * * ERROR: www-client/mozilla-firefox-bin-2.0.0.14 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * mozilla-firefox-bin-2.0.0.14.ebuild, line 63: Called built_with_use 'pkg_setup' 'pkg_setup' 'pkg_setup' '--missing' * eutils.eclass, line 1698: Called die * The specific snippet of code: * [[ -z ${PKG} ]] && die "Unable to resolve $1 to an installed package" * The die message: * Unable to resolve x11-libs/pango to an installed package * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/www-client/mozilla-firefox-bin-2.0.0.14/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-client/mozilla-firefox-bin-2.0.0.14/temp/die.env'. *
Re-fixed, sorry about that :)
