checking for Qt headers... no checking for Qt libraries... no configure: error: Qt development libraries not found See `config.log' for more details. !!! ERROR in app-text/poppler-bindings-0.6.3: !!! In econf at line 1711 !!! econf failed !!! Call stack: !!! * econf (/var/tmp/paludis/app-text-poppler-bindings-0.6.3/temp/loadsaveenv:1711) !!! * src_compile (/var/tmp/paludis/app-text-poppler-bindings-0.6.3/temp/loadsaveenv:3811) !!! * ebuild_f_compile (/usr/libexec/paludis/0/src_compile.bash:49) !!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:463) !!! * main (/usr/libexec/paludis/ebuild.bash:478) diefunc: making ebuild PID 7932 exit with error die trap: exiting with error. Install error: * In program paludis -i --dl-reinstall if-use-changed --debug-build none --log-level warning --continue-on-failure if-independent kpdf: * When performing install action from command line: * When executing install task: * When installing 'app-text/poppler-bindings-0.6.3:0::gentoo': * Install error: Install failed for 'app-text/poppler-bindings-0.6.3:0::gentoo' Reproducible: Always Steps to Reproduce: 1. Try to install anything that depends on poppler-bindings (kpdf, inkscape etc) 2. Receive this error.
So, how about that config.log then ?
Created attachment 162363 [details] config.log Sure thing, here it is.
What is your version of qt3 ? Is it correctly merged ?
> What is your version of qt3 ? 3.3.8-r4 > Is it correctly merged ? Yes, it seems to be. I have konqueror, amarok (all kde3 versions) and so forth running without issues.
please provide emerge --info and emerge -pv poppler-bindings.
[ebuild UD] app-text/poppler-bindings-0.6.3 [0.8.5] USE="cairo gtk* qt3* qt4* -test" 0 kB It's the damnedest thing. It builds just fine using portage with the same use flags that caused paludis to choke. I guess the bug is not in the package then.
yeah if paludis has a problem emerging this ebuild, please see with paludis devs if it's a bug of their own or if indeed the ebuild does something nasty that it shouldn't do.
Please, refer to the following thread in the paludis-user mailing list: http://lists.pioto.org/pipermail/paludis-user/2008-August/000480.html Reopen this if there's something which can be fixed on the poppler or qt side.
this problem is still prevalent in poppler-bindings-0.10.0 The problem is possibly related to paludis appearing to sanitise the ENV variables much more heavily and as a result QTDIR is undefined. however, simply extending "inherit" to have "qt3" in it re-instantiates the QTDIR environment variable, and build continues as normal. the QT3 eclass does this in a highly trivial way however: if [[ -z "${QTDIR}" ]]; then export QTDIR="/usr/qt/3" fi so if one wants to merely place this in the src_configure block that would /possibly/ have the same effect I would assume it works in portage due to the presence of /etc/env.d/50qtdir3 but as far as I am aware, paludis does not simply naively import that directory into build scope. I make a test ebuild that just executed "env" then died in src_configure and ran it under both portage and paludis to compare their ENV's and will attach this for your examination. Notedly I don't use portage any more so the portage specific things such as USE / Compile flags etc will be different. Test Script is as follows: EAPI="2" inherit autotools eutils multilib DESCRIPTION="fake ebuild to test package manager" HOMEPAGE="http://127.0.0.1" LICENSE="GPL-2" SLOT="0" KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd" IUSE="" DEPEND="" src_configure() { env; die; }
Created attachment 169068 [details, diff] Comparason of 2 Environment lists My test ebuild + sort + diff -Naur
