-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 13.03.2013 21:18, schrieb NightStrike: > On Wed, Mar 13, 2013 at 7:22 AM, Corinna Vinschen <[email protected]> > wrote: >> Hi, >> >> I'd like to resurrect a patch which has been refused last year, but I >> think it's still helpful and maybe the opinions have changed a bit. > > Sorry.. did I refuse it? Can you link to the mailing list archive (I > understand that the SF interface blows for that...) > >> For people building just the latest mingw64-headers and mingw64-crt, it's >> kind of surprising that mingw64-crt requires that the headers are already >> installed. In theory, the right thing to do should be that mingw64-crt >> is build after mingw64-headers, and then prefer the just built in-tree >> headers over the already installed headers. > > I'm a little confused here. What we require, ie, the only situation that > we support, is when the version of the headers is the same version of the > crt. Ie, svn checkout revision. Anything outside of that will probably > work, of course, but nobody tests it. > > Now, in terms of the configure test that errors out in the case of not > finding _mingw_mac.h, that is due to the fact that the headers are required > to build the crt. We don't care where they are, we just care that they > exist. If they don't, the crt build will be all fouled up. > > The default, of course, is for the headers to exist in the sysroot that the > crt is getting installed into. This is a fairly common usage pattern, and > modeled after the gcc build. If they're somewhere else instead, you can > just use --with-sysroot=some/wheres/else I just kick in because Corrina is completly right. A common case as for me, is to update the mingw-w64 runtime for an existing installation. So what you want, is to compile the runtime in one go, configue, make, make install. That's impossible for now. At the moment you have to install the headers first and afterwards you are able to build and install the runtime.
For me that work as so: mkdir build cd build ../mingw-w64/configure cd mingw-w64-headers make make install cd .. ../mingw-w64/configure make make install That's not how it should work. The ming-w64 package includes all what is neccessary to build. You don't need already installed headers. This requirement is wrong! You only have to make sure to use the headers included in the package. That's as with any other software package. Really no package I know of requires to install the package headers first to build the package. > > In fact, the help text for with-sysroot even says this: --with-sysroot=DIR > Search for headers within DIR/include > > So if you for whatever reason want to stage a build of mingw-w64-headers in > /tmp/my/dir, you just build the crt with --with-sysroot=/tmp/my/dir That's not the point see above. Even here you have to install the headers first. Cheers Rainer > > Does that not work for you? > > > > >> The below patch does that, unless the --without-headers option is set. >> >> This should work in all typical scenarios: >> >> - cross build gcc: >> >> The headers have to be build first. At the time crt gets build, the >> in-tree headers already have been built for gcc, so they are nicely >> available for the crt build. >> >> - native build gcc: >> >> The installed headers are potentially old. Building crt with the latest >> in-tree headers is preferrable to circumnavigate potential bugs in the >> older headers. >> >> - native mingw-only build: >> >> Same as above. >> >> I can't come up with a scenario in which it would be bad to use the >> in-tree headers, unless you don't build the headers, but crt only. This >> should be fixable, shouldn't it? > > ------------------------------------------------------------------------------ > > 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 > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRQY+WAAoJEB3HOsWs+KJb+hMH/3uwtbVoSvwXo5mlSoFxDaRG R/Suh2GdILBIIX2raque/ZSFgUItcvvrSDulStvvyEk0dCBRn6wq3lijuu87a9U2 NCrLuSfmebrxYYSwFJdVDldCEYvNzefAL8PyUWWXWjVR5OR4qGcooE3CrgbG5Dja 7cgKc6/oURyIyFsFCe5l000D6gjGmFe2KwAwbUBY3WgwWwHVvyonJ6ZJV/nqoQL2 EltzBDBZE5MUMIRQQtwHzYtSc2wVmz5u14js8Iuhtp998q2oqV8OE8q+vnQxj6yU mjUHaOick/tJ88zkuCIzmSdbee+stzHT51YWJtV4XEnScr44yXV9Ectk3F5Ywds= =pH0D -----END PGP 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
