Hello there! You're getting this bug because the package in Summary failed to build in my tinderbox using the gold link editor from binutils. Before closing the bug as INVALID let me explain why this is still important! The gold link editor does not support underlinking of shared objects, which is something I have described in my blog post: http://blog.flameeyes.eu/2010/11/26/it-s-not-all-gold-that-shines-why-underlinking-is-a-bad-thing Even the basic link editor (ld.bfd) has an option to support this but it is a heck to enable and get passed, so linking with gold is simply quicker. Fixing underlinking provides optimized --as-needed builds (because the "softer" version no longer need to recover libraries that are underlinked), so it is a Good Thing To Do. Thank you very much for the attention!
Created attachment 273275 [details] Build log
your blog is down, can you fix?
I prodded my hoster, afraid I had a slashdot effect due to my hurd post :|
Ok, that's nasty. Could you perhaps for the meanwhile briefly explain what underlinking is in a sentence or two?
Should be back up. But in general it means that it leaves the result to link indirectly against one (or more) library it uses the interface of directly. An example with libcanberra would be using XFree (from libX11) without listing it, and assuming it is brought in by libgtk*. In the case of windowmaker, it is using the Fc* functions, which are exposed by libfontconfig, without linking to libfontconfig (it is brought in by libXft). Quick fix: get -lfontconfig in there.
thanks, I see, it misses indirect libs
Is this still a problem with the windowmaker-0.95.* series? I recommend closing as TEST-REQUEST.
I just tested with 0.95.3, libWINGs.so.2.0.1 link command does have -lfontconfig now (with a proper configure check also). So this seems indeed to be fixed in 0.95.x series.
