Hi Erik, > libstdc++ is bundled as a seperate package, darwinx-libstdcxx. The > pre-compiled version from the SDK shouldn't be used. The main goal of > the darwinx toolchain right now is to create self-hosted toolchain which > doesn't depend on binary blobs. I already removed the libstdc++ library > from the SDK's /usr/lib folder, but apparently I forgot to get rid of > the llvm-gcc version as well. > > However, I didn't succeed in getting an x86_64 version of libstdcxx > compiled yet (there's a circular dependency where darwinx-g++ tries to > link against libstdc++ while building libstdc++)
Yes, I noticed this circular dependency problem too. It unfortunately prevented me from going with my first choice of using darwinx-libstdcxx. However, as far as I know, if you remove the llvm-gcc version for i686, it too will have this same circular dependency problem when building darwinx-libstdxx. I think there is a fundamental issue with this rather than it being only a problem for x86_64. Ordinarily, as far as I know, libstdc++ is build during GCC stage2 compilation: http://dev.gentoo.org/~vapier/CROSS-COMPILE-GUTS For now, it seems that I have no choice but to use the binary blob from the Leopard SDK. If you have any better suggestions, please feel free to let me know. Thanks! Paarvai _______________________________________________ mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/mingw
