Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
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
[Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
Hi, This should be already fixed in SVN as of r131472. Still falling over dead on the PPC... http://koji.fedoraproject.org/koji/getfile?taskID=1290915name=build.log The problem seems to manifest if we disable linking against the static libs on PPC and PPC64. Can someone have a look into this please? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
Hi, Building with --disable-static, in addition to producing a slower runtime, is not tested by us so no wonder its not working. Why is this needed on fedora ? Zoltan On Tue, Apr 14, 2009 at 8:59 AM, Paul p...@all-the-johnsons.co.uk wrote: Hi, This should be already fixed in SVN as of r131472. Still falling over dead on the PPC... http://koji.fedoraproject.org/koji/getfile?taskID=1290915name=build.log The problem seems to manifest if we disable linking against the static libs on PPC and PPC64. Can someone have a look into this please? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
Hi, -- Paul F. Johnson Lecturer in Chemistry, Biology and IT FoundatiON Campus Zoltan Varga var...@gmail.com 14/04/09 3:43 PM Building with --disable-static, in addition to producing a slower runtime, is not tested by us so no wonder its not working. Why is this needed on fedora ? Fedora ships with dynamic libs and frowns upon static ones (unless they're really needed). I know I'll get asked this, but why are the static libs needed and is it likely that x86/x86_64 will break in future releases without the static libs? TTFN Paul ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
Hi, Statically linking the mono executable is mostly done to improve the speed of thread-local access, 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 On Tue, Apr 14, 2009 at 5:19 PM, Paul Johnson pjohns...@uclan.ac.uk wrote: Hi, -- Paul F. Johnson Lecturer in Chemistry, Biology and IT FoundatiON Campus Zoltan Varga var...@gmail.com 14/04/09 3:43 PM Building with --disable-static, in addition to producing a slower runtime, is not tested by us so no wonder its not working. Why is this needed on fedora ? Fedora ships with dynamic libs and frowns upon static ones (unless they're really needed). I know I'll get asked this, but why are the static libs needed and is it likely that x86/x86_64 will break in future releases without the static libs? TTFN Paul ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
Hi, Statically linking the mono executable is mostly done to improve the speed of thread-local access, 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. Not with you here. Are you saying that we need to enable statics while building but don't need to include them in the final package? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
Exactly. Zoltan Not with you here. Are you saying that we need to enable statics while building but don't need to include them in the final package? TTFN Paul -- Sie können mich aufreizen und wirklich heiß machen! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
On Tue, 14 Apr 2009 16:19:45 +0100 Paul Johnson pjohns...@uclan.ac.uk wrote: Fedora ships with dynamic libs and frowns upon static ones (unless they're really needed). I know I'll get asked this, but why are the static libs needed and is it likely that x86/x86_64 will break in future releases without the static libs? I'll bet mono-debugger is broken in your current releases on x86/x86_64 already. We (Gentoo) found that to be the case. Mono-debugger would just go sit in a corner and sulk unless mono was built with static libs. /loki_val ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Problem with PPC/PPC64 and disabling builds against the static libs
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 Hi, 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 :-). -Toshio ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
