GNOME Bugzilla – Bug 581559
gnote compilation troubles with LDFLAGS=-Wl,--as-needed is used
Last modified: 2009-06-05 19:44:17 UTC
Gnote does not complete configure and/or build successfully when LDFLAGS=-Wl,--as-needed is used. Configure issue is easy - m4/boost.m4 needs to be updated with latest boost.m4 macro from http://repo.or.cz/w/boost.m4.git
Created attachment 134082 [details] [review] [PATCH 1/2] Update boost.m4 macro to latest version.
Created attachment 134083 [details] [review] [PATCH 2/2] Reorder libs so it builds with --as-needed ldflags.
the lastest boost.m4 fails here, so upgrading is a no go. applied the second patch.
do you really need these flags?
(In reply to comment #4) > do you really need these flags? > Not really, but about 50% of Gentoo users are using them, as it makes things a bit more manageable when some basic lib decides to change soversion (and thus breaking everything that has been linked against it). See this blog post for an example: http://blog.flameeyes.eu/2008/11/19/relationship-between-as-needed-and-no-undefined-part-1-what-do-they-do Why/how does the boost check fail for you?
(In reply to comment #4) > do you really need these flags? The benefits of it are explained at http://www.gentoo.org/proj/en/qa/asneeded.xml And it is something that tends to get applied globally for all builds. Most commonly used packages succeed with it these days in our distribution and benefits are gained globally. Mostly just more exotic or dead upstream packages still fail with it nowadays as seen at https://bugs.gentoo.org/showdependencytree.cgi?id=as-needed&hide_resolved=1 - and gnote too.
(In reply to comment #5) > Why/how does the boost check fail for you? > boost.m4 "make check" just fail here. I reported it to upstream. But so far no idea. Now it could just be that the test are broken.
committed the patch. it seems to not break here.