This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: solaris 2.7 binutils problem
- To: Wolfgang Bangerth <wolfgang dot bangerth at iwr dot uni-heidelberg dot de>
- Subject: Re: solaris 2.7 binutils problem
- From: "Nils Lohner" <lohner at debian dot org>
- Date: Thu, 27 Sep 2001 15:03:53 +0200
- Cc: gcc-bugs at gcc dot gnu dot org
On Thu, 27 Sep 2001 14:43:30 +0200 (MET DST), Wolfgang Bangerth wrote:
>
>Nils Lohner wrote:
>> Well, another failed attempt. PLEASE make the build process fail on a
>> configure instead of breaking in the compile process. For people who
>> don't often build compilers it'll save much time...
>>
>> --with-gnu-as doesn't seem to work as you'd expect, so even reading the
>> INSTALL guides online and applying them can result in errors.
>>
>> Here I tried to be clever and use:
>> /sup/build/gcc-3.0.1/build > ../configure --prefix=/sup --with-gnu-ld --with
>-gnu-nm --with-gnu-as
>
>Well, that's probably why http://gcc.gnu.org/install/configure.html
>states:
>--with-gnu-as
> Specify that the compiler should assume that the assembler it finds
> is the GNU assembler. However, this does not modify the rules to find an
> assembler and will result in confusion if found assembler is not
> actually the GNU assembler. (Confusion will also result if the compiler
> finds the GNU assembler but has not been configured with
> --with-gnu-as.) If you have more than one assembler installed on your
> system, you may want to use this option in connection with --with-as=path
>name.
>--with-as=pathname
> Specify that the compiler should use the assembler pointed to by
> pathname, rather than the one found by the standard rules to find an
> assembler, which are:
> [...]
>
>You have to use both options. Same for GNU ld.
Sigh. OK, I'll give it the path etc. for ld and as and nm. I still
argue that before any of these are used in the build process they should
be checked to ensure that they match expectations. I don't understand
the build process well, but these errors really need to show up in a
failed configure. That would have avoided my mails on the subject and
saved me a few days of attempted gcc builds.
Thanks for bearing with me. Please catch these issues in the
configurations somewhere if at all possible. It'll save some people
several headaches :)
Thanks.
Nils.
PGP signature