This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: NM and AR not being used?
- From: Georg Schwarz <geos at epost dot de>
- To: Jim Wilson <wilson at specifixinc dot com>
- Cc: Georg Schwarz <geos at epost dot de>, gcc at gcc dot gnu dot org
- Date: Thu, 8 Jul 2004 20:40:23 +0200 (CEST)
- Subject: Re: NM and AR not being used?
Thanks for your reply!
> Georg Schwarz wrote:
> > env AR=/usr/local/mips-sgi-irix5.3/bin/AR
> > NM=/usr/local/mips-sgi-irix5.3/bin/nm
> > RANLIB=/usr/local/mips-sgi-irix5.3/bin/ranlib CONFIG_SHELL=/bin/ksh
> > /usr/people/schwarz/gcc-3.4.0/configure --prefix=/usr/local
> > --with-gnu-as --with-gnu-ld --with-as=/usr/local/mips-sgi-irix5.3/bin/as
> > --with-ld=/usr/local/mips-sgi-irix5.3/bin/ld
> > --enable-languages=c,c++,ada
>
> The easiest way to make this work is to build and install binutils using
> the exact same prefix that you build and install gcc with. If you do
that is unpack binutils into /usr/people/schwarz/ in this case?
> this, then gcc will automatically find and use the installed binutils.
> You won't need the --with-as= and --with-ld= configure options.
>
> Normally, only cross compilers need to worry about the value of AR/NM,
> and if you are building a cross compiler, you can't use a bootstrap
> rule. You have to use make all. If you do a make all-gcc, you will see
> that gcc uses the AR/NM that you specified, because the toplevel
> Makefile passes down the proper values for them.
>
> However, when you use the bootstrap rule, the toplevel Makefile isn't
> passing down the values of AR/NM, so gcc doesn't use the ones you
> specified. This doesn't seem like an serious problem, so I'd suggest
> filing a bugzilla bug report. You can work around it by setting your
since you seem to understand the problem much better than I do, could
you please file that bug report? Thanks.
> path before building gcc.
>
> The errors you get are because the GNU tools don't support all of the
> features of the SGI tools. These errors should be pretty harmless. It
> is probably better to use GNU/SGI tools consistently to avoid these
> errors though.
> --
> Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
>
>
>
>
--
Georg Schwarz http://home.pages.de/~schwarz/
geos@epost.de +49 177 8811442