Hi Erik, >> Okay, I was originally confused since x86_64 objects could be compiled >> successfully but the linking that failed. Good to know that you are >> already aware of this and are actively working on finishing it. I'll >> look forward to your update in the next day or so. > > I just looked into it and apparently Apple did something ugly to get > x86_64 support in GCC. Instead of creating a compiler for the > x86_64-apple-darwin9 target they integrated x86_64 support in the > i386-apple-darwin9 target... This could also be the reason why only the > linker step fails for you. I don't know how Apple managed to do this so > for now I'm resorting to a seperate x86_64-apple-darwin9 target.
Hm...simply because they shoehorned x86_64 support into i386-apple-darwin9 does not necessarily prevent the possibility to use a single compiler for both i386 and x86_64 architectures. After all, we do exactly that with x86_64-redhat-linux-gcc on Fedora Linux. The only difference is that the primary compiler is x86_64, rather than i386 in Apple's case. The question is whether a natively hosted Mac OS X compiler can do what we come to expect on Linux. I have not tried it yet, but I can check that out later today. I think the linking is failing because either the libc installation step was not done properly to provide crt3.o/libgcc.a in the right paths, or the GCC is not picking up the paths properly (bad specs), or both. Here is a reference regarding the standard process of making a cross-compiler. You are probably quite familiar with all of these steps. http://dev.gentoo.org/~vapier/CROSS-COMPILE-GUTS Finally, this is another reference that I had found regarding OS X x86_64 target support on a Linux host: http://devs.openttd.org/~truebrain/compile-farm/apple-darwin9.txt This reference also seems to indicate that a separate x86_64 compiler is built rather than combining that target into the i386 compiler. Ideally we'd have one compiler that can handle them both, but I fully appreciate, especially given my own experiences dealing with Apple's odcctools and GCC, that what we take for granted for Linux and Windows targets may not be possible for Mac OS X. :) I'm sure you are very familiar with all of the above, but I figured I'd rehash some of this for the benefit of passive readers of this list! Thanks! Paarvai _______________________________________________ mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/mingw
