Re: [PATCH 01/10] gnu: cross: Use CROSS_*_INCLUDE_PATH for system headers.

[Andy Wingo]

On Tue 03 May 2016 14:06, address@hidden (Ludovic Courtès) writes:

> Andy Wingo <address@hidden> skribis:
>
>> And why just one CROSS_C_INCLUDE_PATH -- would it not be necessary in
>> theory to have such a CROSS_ARCH_... for each ARCH that we might be
>> interested in?  I am not suggesting that you make the change now but I
>> want to know what the right thing is :)
>
> In theory, you’re right.  That’s one of the concerns that was raised:
>
>   http://gcc.gnu.org/ml/gcc/2013-02/msg00125.html
>
> I don’t think it’s a common use case though.

I dunno.  You could certainly manage to install a mingw toolchain and an
AVR toolchain into a profile by mistake.  It's a bad idea of course, and
we wouldn't warn about it, and the failure would be weird.  The
mitigating factors are that you rarely need to actually have a
cross-compiler in a profile because cross-builds can just include them
automatically, and also you can use environments -- but it's something
that people need to add to their mental model, and something we should
document in the pending "cross-compiling from guix" section of the
manual :)

Andy