CROSS-COMPILATION!!! pkg-config is a binary and thus cannot be run on the CBUILD. Most (at least all I used until now) configure scripts propose to check for the packages own config (e.g directfb-config) before falling back to use pkg-config to gather library information. ALL ebuilds need to get the path to the dependency config script (e.g DIRECTFBCONFIG=/path/to/directfb-config for libsdl) as a configure option for cross compilation. Reproducible: Always Steps to Reproduce: 1. emerge libsdl for CHOST != CBUILD 2. 3. Actual Results: libtool searches for its dependent .so files in the wrong directories (some of them are wrong because of bug:275462) Expected Results: libtool searches for all .so files in the correct directory
Please include a sample build.log and emerge --info and version of pkg-config.
Feel free to reopen this bug yourself, when you'll give us more informations
Pkg-config version is: dev-util/pkgconfig-0.23 I cannot include a build.log or emerge --info of that system because i finished the project and wiped that toolchain from my hdds. My CFLAGS, CXXFLAGS were meager "-O -pipe", close to no use-flags at all, icu and unicode plus some only for my binary of interest (origyn web browser). The build log would show nothing. The effect was that the configure script tries to invoke pkg-config, which fails, because the binary being invoked is build for ppc and my cpu is a core2. So the configure script gets no output from pkg-config and assumes that there is no such package installed. For an example you can open the configure script for libsdl search for pkg-config (2nd match - should be around line 30000) and see what the configure script does. I hope those are enough informations, sorry to have not more... on my portage tree those bugs are fixed (see description) only wanted to give some help back to the team providing me with my OS - if its no help for you simply close it again.
Try 0.25 (now in portage), it fixed another cross-compilation bug our bugzilla had open...
