Toshio Kuratomi <a.badger <at> gmail.com> writes: > > 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? >
A little poking looks like I was right about this problem :-( On ppc, with the statically compiled mono-2.4 final, trying to use the embedding samples yields this: cd mono-2.4/samples/embed gcc -o teste teste.c `pkg-config --cflags --libs mono` -lm mcs test.cs ./teste test.exe Segmentation fault And: cd mono-2.4/samples/embed gcc -Wall -o test-invoke test-invoke.c `pkg-config --cflags --libs mono` -lm mcs invoke.cs ./test-invoke invoke.exe Segmentation fault -Toshio _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
