On 3/14/2013 18:41, Ruben Van Boxem wrote: > 2013/3/14 Corinna Vinschen <[email protected]> > >> On Mar 14 11:13, [email protected] wrote: >>> >>>> >>>> You *have* to install the headers first as a prerequisite for the crt >> to >>>> work. There are generated headers required for the CRT, not a plain and >>>> simple -I. >>> >>> Many packages generate headers or some sources. Consider config.h.in -> >>> config.h as the most common case. I cannot see that as a reason for >>> increased build complexity. There just implies one extra level of >>> dependencies in (generated) Makefile.
Some of the library headers are designed to overwrite default copies from mingw-w64-headers, not a simple config.h, eg winpthreads. >> >> Exactly. Also, the just built headers *are* taken into account by my >> patch, because they are included as well. I don't see why we need a >> two stage build at all, if a one stage build can do the right thing >> out of the box. >> I'm still not sure about saving a few keystrokes for convenience to justify the increased maintenance. Now you have *two* build systems to take care of. > > The two stage build is only required to be possible in the case of building > a Canadian Cross, in which the build sequence is > headers,binutils+gcc-c,crt,gcc-all. But it is indeed not necessary at all > when there's a preexisting gcc available. Don't forget about doing a clean bootstrap with no cross gcc available.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
