Some packages cannot ./configure because x11-libs/qt sets PKG_CONFIG_PATH in /etc/env.d/45qt3 This is the only package which does this (on my system), thus PKG_CONFIG_PATH="/usr/qt/3/lib/pkgconfig". The packages, that cannot ./configure are part of asfsdf-meta-bundle-2.0.1RC2-precollected.tar.gz from http://www.meta-environment.org/ (currently not in portage). Reproducible: Always Steps to Reproduce: 1. wget http://homepages.cwi.nl/~daybuild/releases/asfsdf-meta-bundle-2.0.1RC2-precollected.tar.gz 2. tar zxf asfsdf-meta-bundle-2.0.1RC2-precollected.tar.gz 3. cd asfsdf-meta-bundle-2.0.1RC2RC2/toolbuslib-0.9 4. ./configure Actual Results: [...] checking if PKG_CONFIG_PATH needs to be extended for bundled packages... no checking whether location of aterm is explicitly set using --with-aterm... no checking for ATERM... yes checking prefix of package aterm... /usr checking the transitive closure of dependencies of aterm... configure: WARNING: No pkg-config file found for aterm <--- hanging here Expected Results: [...] checking if PKG_CONFIG_PATH needs to be extended for bundled packages... no checking whether location of aterm is explicitly set using --with-aterm... no checking for ATERM... yes checking prefix of package aterm... /usr checking the transitive closure of dependencies of aterm... aterm [...] I'm about to create a set of ebuilds for the meta-environment. I can workaround the problem by unsetting PKG_CONFIG_PATH in src_compile, just before econf (qlist qt|xargs rm ;-)). Maybe it's a bug in the packages' build-system (autoconf-2.59), as it operates directly on the variable and doesn't look in the default pkg-config search-path, if PKG_CONFIG_PATH doesn't contain useful information.
(In reply to comment #0) > Maybe it's a bug in the packages' build-system (autoconf-2.59), as it operates > directly on the variable and doesn't look in the default pkg-config > search-path, if PKG_CONFIG_PATH doesn't contain useful information. Pretty much. The entry is needed there; sorry, tell upstream to fix their configure scripts, we cannot remove it, it would breaks lots of stuff
While this is more an upstream bug..
..there's nothing holding us back, installing the pkgconfig file in the standard path or symlinking to it.
(In reply to comment #3) > ..there's nothing holding us back, installing the pkgconfig file in the > standard path or symlinking to it. Except for the slotting, huh?
Qt 3 and 4 do not install conflicting pkgconfig files.
Created attachment 193725 [details, diff] Patch to qt-3.3.8b-r1.ebuild to install pkgconfig file in standard location This patch modifies the qt3 ebuild to install the pkgconfig file in the standard /usr/lib/pkgconfig/ dir and to not add the PKG_CONFIG_PATH variable to env.d. I built qt3 with this patch and then built psi-0.10 (a pure qt3 app) against it, after verifying that ${T}/environment does not contain PKG_CONFIG_PATH.
The fix is in x11-libs/qt-3.3.8b-r2, please reopen if the problem persists with that version.
