On 10/13/2013 05:24, Alon Bar-Lev wrote: > Hi, > > Is there any advantage of keeping mingw-w64-libraries and > mingw-w64-tools at same package as the crt? >
Heard you the first time. > These cannot be compiled if there is no fully functional toolchain. > > Following sequence does not work: > > 1. binutil > 2. crt headers > 3. gcc-stage1 > 4. crt --with-libraries --with-tools > > The libraries and tools also seems not to be tight coupled with the crt. > You seem to be confusing the CRT with the entire package. The top level configure is a very recent development compared to the rest, for now, it is a rather poor replacement to build the components separately, traditionally, it is done: binutils headers gcc-stage1 crt the rest of gcc the rest of the libraries and tools. > Any reason why not to publish these as separate packages? > Mostly because everything goes under /trunk, and a release is just svn export.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
