DJ Delorie writes:
>> OK, but what's wrong --with-sysroot=/ ?
>
> It should work, it just seems "wrong" for a native compiler to have a
> sysroot...
I agree that it's a bug, but I'm not sure I think it's the same bug that
you think it is. Every toolchain has a sysroot, really. I think it's a
On Thu, Mar 15, 2012 at 9:50 PM, DJ Delorie wrote:
>
>> OK, but what's wrong --with-sysroot=/ ?
>
> It should work, it just seems "wrong" for a native compiler to have a
> sysroot...
I noticed that a lot of binutils tests fail if it is not compiled with
--with-sysroot=/ . This is why I always c
> OK, but what's wrong --with-sysroot=/ ?
It should work, it just seems "wrong" for a native compiler to have a sysroot...
DJ Delorie writes:
>> My first try would be --with-build-sysroot. Does that fail in some way?
>
> It's ignored without --with-sysroot, but if you use --with-sysroot,
> the cross-built native *also* expects to use a sysroot, which means
> binutils must also be built with a sysroot, even if its "/
> My first try would be --with-build-sysroot. Does that fail in some way?
It's ignored without --with-sysroot, but if you use --with-sysroot,
the cross-built native *also* expects to use a sysroot, which means
binutils must also be built with a sysroot, even if its "/".
DJ Delorie writes:
> configure has various ways of specifying the target headers for a
> cross-compiler. However, none of these work when you're
> cross-building a native (build!=host==target). Unfortunately,
> configure looks in $target_header_dir for target headers to determine
> various bits
