On Thu, Aug 5, 2021, at 8:30 AM, Michael Matz wrote:
> Hello,
>
> On Wed, 4 Aug 2021, John Ericson wrote:
>
> > On Wed, Aug 4, 2021, at 10:48 AM, Michael Matz wrote:
> > > ... the 'as' and 'ld' executables should be simply found within the
>
On Wed, Aug 4, 2021, at 10:48 AM, Michael Matz wrote:
> ... the 'as' and 'ld' executables should be simply found within the
> version and target specific GCC libexecsubdir, possibly by being symlinks
> to whatever you want. That's at least how my crosss are configured and
> installed, without a
On Wed, Aug 4, 2021, at 3:32 AM, Jonathan Wakely via Gcc wrote:
>
> Doesn't GCC automatically look for those commands in the --prefix directory
> that you configure GCC with? Or is that only for native compilers?
>
It will search only if --with-*=... was not passed, and it will never prefix
the
Problem:
It's somewhat annoying to have to tell GCC --with-as=... --with-ld=... just to
prefix those commands the same way GCC is prefixed.
In particular, when doing host-only build (skipping all target libraries), one
otherwise doesn't need the target-specific binutils to be yet built, but
--
Hello Binutils and GCC lists[1],
I would like to propose that GNU tools consistently interpret configs with
"netbsd" as meaning ELF as opposed to a.out. Currently, newer CPUs do that, but
older ones have "netbsd" mean a.out for historical reasons, and "netbsdelf" is
used instead. This inconsist
