Ralf Corsepius skribis:
> On 02/13/2013 03:49 PM, Ludovic Courtès wrote:
[...]
>> At any rate, there’s a need for similar env. vars for cross-compilers. WDYT?
> I am having difficulties to imagine such a need.
Well, for the same reason that CPATH & co. are sometimes needed, or at
least conven
On 02/14/2013 04:37 PM, Ralf Corsepius wrote:
>> At any rate, there’s a need for similar env. vars for cross-compilers. WDYT?
> I am having difficulties to imagine such a need.
Indeed: I've experienced that environment variables are fine to test something
out,
but open a can of worms when used
On 02/13/2013 03:49 PM, Ludovic Courtès wrote:
Richard Biener skribis:
On Wed, Feb 13, 2013 at 12:13 PM, Richard Biener
wrote:
On Tue, Feb 12, 2013 at 9:41 PM, Ludovic Courtès wrote:
Joel Sherrill skribis:
But it still doesn't address the situation where you have multiple
cross compiler
Richard Biener skribis:
> On Wed, Feb 13, 2013 at 12:13 PM, Richard Biener
> wrote:
>> On Tue, Feb 12, 2013 at 9:41 PM, Ludovic Courtès wrote:
>>> Joel Sherrill skribis:
>>>
But it still doesn't address the situation where you have multiple
cross compilers in your PATH all for differ
On Wed, Feb 13, 2013 at 12:13 PM, Richard Biener
wrote:
> On Tue, Feb 12, 2013 at 9:41 PM, Ludovic Courtès wrote:
>> Joel Sherrill skribis:
>>
>>> But it still doesn't address the situation where you have multiple
>>> cross compilers in your PATH all for different targets.
>>
>> Yeah, I thought
On Tue, Feb 12, 2013 at 9:41 PM, Ludovic Courtès wrote:
> Joel Sherrill skribis:
>
>> But it still doesn't address the situation where you have multiple
>> cross compilers in your PATH all for different targets.
>
> Yeah, I thought about it, but couldn’t come up with a practical use case
> where
Joel Sherrill skribis:
> But it still doesn't address the situation where you have multiple
> cross compilers in your PATH all for different targets.
Yeah, I thought about it, but couldn’t come up with a practical use case
where you’d need to use different cross-compilers in a single build.
Lud
On 2/12/2013 12:48 PM, Ludovic Courtès wrote:
Hi,
GCC honors CPATH, LIBRARY_PATH, & co. regardless of whether it’s built
as a cross-compiler.
Consequently, when cross-compiling a package that contains both support
tools to be compiled natively and the main code to be cross-compiled,
these varia
Hi,
GCC honors CPATH, LIBRARY_PATH, & co. regardless of whether it’s built
as a cross-compiler.
Consequently, when cross-compiling a package that contains both support
tools to be compiled natively and the main code to be cross-compiled,
these variables are useless because they don’t allow host a
