On Wed, Mar 13, 2013 at 7:22 AM, Corinna Vinschen <vinsc...@redhat.com> 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
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
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
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
