This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Yann, Titus, all, 2011/6/24 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>: > What does the MacOS-X' ld says to used static/shared libraries? GNU ld > at least supports the equivalents: > - for static: -Bstatic  -dn Â-non_shared  -static > - for shared: -Bdynamic Â-dy Â-call_shared > If you can find a common option for both, then the better. To the best of my knowledge, Apple's ld supports -static and -dynamic. Man page for ld states that -dynamic The default. Implied by -dylib, -bundle, or -execute -static Produces a mach-o file that does not use the dyld. Only used building the kernel. though trying to compile a sample hello world results in a not working executable (segfaults) even if file reports it being a "Mach-O 64-bit executable x86_64". So I'm not sure it's an option. Anyways I could get past the point in my original email by not forcing libstdcxx to be linked statically. Like Titus, I'm not really sure why we should consider linking gcc statically against libstcxx (and at this point I can say I chose that option with no knowledge about it, just because it sounded nice :). As for my newest error, Titus, that was the actual error. You can find the build.log at http://www.morpheu5.net/build-20110626-0.log see if you can spot something more than me. -- Andrea -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |