This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC/RFA] --with-build-time-tools configure option
dj@redhat.com (DJ Delorie) wrote on 05.01.06 in <200601052149.k05LnPQl023711@greed.delorie.com>:
> Of course, that applies mostly to --host tools. For target tools it's
> a bit more consistent, although "traditionally" gcc finds its tools in
> a different location than the user does - it looks for $target/bin/as
> but the user often uses $target-as instead, and there are more
> $target-foo tools than $target/bin/foo ones.
And that broke I forget what build, so I currently add a step linking the
ones to the others where missing. (Obviously something that needed to use
one of the missing tools and wasn't prepared to use the $target- names.)
To state it another way, $target-gcc is useful to have in your $PATH all
the time, and $target/bin/gcc is useful to put into $PATH for the duration
of some cross-compiles ... and that's true for all tools.
Is there a good reason for the discrepancy?
MfG Kai