I'm reporting this bug because the package in summary fails to build when forcing --as-needed on through spec files (check out http://blog.flameeyes.eu/2008/11/14/problems-and-mitigation-strategies-for-as-needed for details). Please note that this bug _might_ apply to -Wl,--as-needed in LDFLAGS as well; in both cases it should be fixed. Also, if this is due to the package in question not respecting user-defined LDFLAGS, you should get to fix that too. Check the attached build log. Thanks, Diego
Created attachment 198309 [details] Build log
Fails also with LDFLAGS="-Wl,--as-needed" in the test suite; the same way.
IMHO it's not just the make check, the Python binding seems to be just broken, lacking a link to libraptor or something.
Created attachment 198330 [details, diff] Part of the solution. Problem with this is that then CORE.so from perl -bindings get built without LDFLAGS, so from one problem to another.
Settings LDFLAGS to LIBS does not look right to me to be honest...
(In reply to comment #5) > Settings LDFLAGS to LIBS does not look right to me to be honest... > Makefile.am's set AM_LDFLAGS=@LIBRDF_LDFLAGS@ $(MEM_LIBS) etc., but they have $(LDFLAGS) as used separately so AFAIK it's only the name that must be bothering you here (it bothers me too a bit) but anyway, that isn't the problem with CORE.so in perl/ directory.. It's using both Makefile.am and Makefile.PL, and I couldn't get the LDFLAGS passed into the Makefile.PL which generates the Makefile, it must be something _very_ simple.
Errrr AM_LDFLAGS should _not_ list libraries!
1.0.10.1 still fails, I've added a workaround to the ebuild to avoid broken python bindings being installed and a comment to the ebuild. Leaving open for correct resolution...
Comment on attachment 198330 [details, diff] Part of the solution. Pretty bogus.
Nevermind. Fixed it properly.
