-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kai Ruottu wrote: > Because all the MinGW target libs already were produced during the step > 1, it should > sound being "reinventing the wheel" to try to reproduce these during the > step 2.... > So one uses the 'make all-gcc', and gets only the "GCC" binaries for the > new host. > That there would be any problems in reproducing the extra libraries will > remain totally > unnoticed...
If I understand you correctly, you're saying that the target runtime libraries are already created by the cross-compiler in Phase 1, so I don't need to rebuild them again in Phase 2 along with the crossed-native compiler - I can get by by just building the compiler. I don't know much about the internals of GCC, but what you're saying should be possible though a bit cumbersome. Building everything in Phase 2 (compiler and libraries) just gives a nice bundle that I can then redeploy as I wish (but this is precisely the thing that seems to be broken, on MinGW at least). Thanks, Ranjit. - -- Ranjit Mathew Email: rmathew AT gmail DOT com Bangalore, INDIA. Web: http://rmathew.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFETHRVYb1hx2wRS48RAlCgAJsH3Vr2Ns2DkqXRb/QOzQsrzUaU+ACgiLE0 3IGHUaZ+230w3MP0Q4WfpqQ= =kyo9 -----END PGP SIGNATURE-----
