[Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs

Toshio Kuratomi a.badger at gmail.com
Tue Apr 14 20:47:23 EDT 2009

Zoltan Varga <vargaz <at> gmail.com> writes:

> Hi,  Statically linking the mono executable is mostly done to improve the
speed of thread-localaccess, to ease debugging etc. Note that only libmono is
linked statically into the runtime,the other dependencies like libglib are not.
If fedora doesn't like static libs, you can omit them from the package, while
still building them.                           Zoltan


The package I've just built for Fedora does this (links /usr/bin/mono against
the static libmono.a and then removes the static libraries prior to finishing
the package).  The concern I have with this strategy long-term is that programs
wanting to embed the mono runtime will be linking against the dynamic
libmono.so.  If this is causing issues for /usr/bin/mono and we don't know what
the trigger is, isn't this a potential problem for them as well?

Note that I'm not a mono user, I'm just jumping in to make sure we get mono-2.4
packaged in time for the next release.  So feel free to correct me if I
misunderstand something :-).


More information about the Mono-devel-list mailing list