When trying to emerge enlightenment-0.16.9999 it fails give this error: checking for pkg-config... /usr/bin/pkg-config checking for imlib2 >= 1.2.0... Package @requirements@ was not found in the pkg-config search path. Perhaps you should add the directory containing `@requirements@.pc' to the PKG_CONFIG_PATH environment variable Package '@requirements@', required by 'imlib2', not found configure: error: Library requirements (imlib2 >= 1.2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/enlightenment-0.16.9999/work/e16/e/config.log
Created attachment 51986 [details] The config.log file for the failed ebuild
you neglected to post `emerge info` if configure has '@requirements@' it means the autotools werent run correctly
Created attachment 51989 [details] my "emege info"
try posting the log from `emerge enlightenment >& log`
Created attachment 51993 [details] emerge enlightenment-0.16.9999 >& log
you could try maybe `export WANT_AUTOMAKE=1.9 WANT_AUTOCONF=2.5` and see if that helps
I tried `export WANT_AUTOMAKE=1.9 WANT_AUTOCONF=2.5` and I get the same error when trying to emerge.
Me too. checking where the gettext function comes from... libc Sound support has been turned off, per the --enable-sound=no passed to your configure line. checking for pkg-config... /usr/bin/pkg-config checking for imlib2 >= 1.2.0... Package imlib2 was not found in the pkg-config search path. Perhaps you should add the directory containing `imlib2.pc' to the PKG_CONFIG_PATH environment variable No package 'imlib2' found configure: error: Library requirements (imlib2 >= 1.2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. !!! ERROR: x11-wm/enlightenment-0.16.9999 failed. !!! Function econf, Line 449, Exitcode 1 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message.
what version of imlib2 do you guys have ? do you have imlib2.pc in /usr/lib/pkgconfig/
I have : imlib2-1.2.0-r1
Okay, here's the deal. I don't have imlib2 in my system. It appears as if your emerge assumes it is there. So I then emerged imlib2 into my system.... Okay, all nicely merged with no errors. It is the version imlib2-1.2.0-r1... Now when I try to build I get: checking for imlib2 >= 1.2.0... Package @requirements@ was not found in the pkg-config search path. Perhaps you should add the directory containing `@requirements@.pc' to the PKG_CONFIG_PATH environment variable Package '@requirements@', required by 'imlib2', not found configure: error: Library requirements (imlib2 >= 1.2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. !!! ERROR: x11-wm/enlightenment-0.16.9999 failed. Same problem, different route.
seems imlib2-1.2.0-r1 produces a .pc file with '@requirements@' in it ... the unstable/cvs versions have this fixed
Is "the unstable/cvs version" of imlib2 in portage? imlib2-9999.ebuild ? or imlib2-1.2.0.20050220.ebuild ?
I just edited /usr/lib/pkgconfig/imlib2.pc to remove -Requires: @requirements@ +Requires: Don't know where it came from, but it fixed it.
fixed in imlib2-1.2.0-r2
Don't know if this is relevant to the "fixed in imlib2-1.2.0-r2" comment, but re-emerging that version doesn't fix the existing /usr/lib/pkgconfig/imlib2.pc if it contains the @requirements@ error.
*** Bug 122245 has been marked as a duplicate of this bug. ***
As seen in Bug 122245 and its two duplicates this is broken again. I have two systems, one x86 which upgraded enlightenment without trouble, but the second, an amd64 failed with the @requirements@ bug. The cause is, that the ebuild contains: dosed "s:@requirements@::" /usr/lib/pkgconfig/imlib2.pc But on amd64 imlib2.pc is installed into /usr/lib64 so I still get a broken .pc file.
> As seen in Bug 122245 and its two duplicates this is broken again. no, it was never fixed properly in the first place ive committed the fix to 1.2.0 and will move a newer snapshot to stable
