This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: target_header_dir vs host-x-host
- From: DJ Delorie <dj at redhat dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: binutils at sourceware dot org
- Date: Fri, 16 Mar 2012 13:35:25 -0400
- Subject: Re: target_header_dir vs host-x-host
- References: <201203160412.q2G4C6DV025456@greed.delorie.com> <mcrr4wtw4rt.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <201203160431.q2G4V6ZC025872@greed.delorie.com> <mcrmx7hw3tf.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <201203160450.q2G4oZGg026253@greed.delorie.com> <mcripi4wv8j.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
moving to binutils for this...
> >> 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
> bug that GNU ld only accepts the --sysroot option if configured with
> --with-sysroot. The default sysroot for a native toolchain is /. That
> should be the default even for the unusual case of cross-building a
> native toolchain. Right now it isn't, but the bug is not that the
> sysroot is /, it's that the sysroot has to be explicitly specified.
>
> Ian
Maybe we should consider making sysroot *always* enabled, with a
default of "/" then?