Linking Issue
Moderator: Committer
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Linking Issue
Reported on sourceforge: https://sourceforge.net/p/freeorion/bugs/566/
Re: Linking Issue
I'm not sure what portion of that discussion you're referring to (unless simply the broad idea that the optimized libraries wind up much smaller than the debug libraries). It seems to me that this issue stems totally from the fact that since libfreeorioncommon.so is not intended as a general purpose shared library we have been content to rely on the fact that all our executables would also be linked with libfreeorionparse.so and so had not been linking libfreeorioncommon.so with libfreeorionparse.so.vincele wrote:Seems related to issues talked about in there
It's also my impression that it's actually Mageia's default flag -Wl,--no-undefined that is triggering this error rather than -Wl,--as-needed
Anyway, I'm probably just writing here from some urge to post moreso than a true contribution of expertise; I'll be glad to leave the response on this issue to Marcel.
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: Linking Issue
You're probably right. common and parse are circular referencing to each other. Adding -Wl,--allow-shlib-undefined for common should fix this.Dilvish wrote:It's also my impression that it's actually Mageia's default flag -Wl,--no-undefined that is triggering this error rather than -Wl,--as-needed
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz