------- Comment #7 from gin at mo dot msk dot ru 2006-12-29 14:35 -------
Subject: Re: -B$(build_tooldir)/bin/
> Can you give the output of the original confgure which should show you which
> ld/as GCC is going to use?
No. Version 4 just does not build on that system at all (or this
requires essentially reimplementing the support of the system in gcc).
So the question must be about the same older one that I already wrote
about. It does not report that - unlike 4.0.2, 4.1.1.
That is, in it `gcc/config.log' says nothing about that. Re- ran
`gcc/configure' with the same options as `config.status --r' would do
(created another directory for that). Neither it said anything about
that. It would not even report is the linker it found gnu one or not.
> By default the toplevel configure looks into PREFIX/${TARGET} for ld/as.
Looks like `xgcc' of old version actually does that. Even without
that `-B' option, but with `ld' in that directory existing, it
outputs:
PREFIX/lib/gcc-lib/i586-pc-sco3.2v5.0.4/3.0.3/../../../../i586-pc-sco3.2v5.0.4/bin/ld:
unrecognized option '-YP,/usr/ccs/lib:/lib:/usr/lib'
PREFIX/lib/gcc-lib/i586-pc-sco3.2v5.0.4/3.0.3/../../../../i586-pc-sco3.2v5.0.4/bin/ld:
use the --help option for usage information
collect2: ld returned 1 exit status
That is, looked for `ld' in in directory based on its own installation
one. This is equivalent of `-B$(build_tooldir)/bin/', and does
exactly the same harm.
The worst is that could not have foreseen that by documentation. This
directory was even missing in <standard rules> in `--with-as'
description in that version of `gcc/doc/install.texi'. That file
would mention only
@[EMAIL PROTECTED]/lib/gcc-lib/@var{target}/@var{version}} and
<operating system specific directories>.
> use --with-ld/--with-as.
It is a workaround at best (will try it for 3.0.3). Programs
installed even in the same PREFIX are not necessarily intended for
gcc. Certainly options passed to program must match the type of
program configuration chose. The very use of gnu ld on non- gnu
system when neither `--with-ld' nor `--with-gnu-ld' are specified is
at least suspicious and should issue warning.
The lack of a standard way to figure which `as', `ld' are used is also
bug, and already fixed in 4.
> No, I still say you are incorrect.
Thus partly agree with that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28472
