Re: gcc 3.1 installation

[Jeff Sturm <jsturm at one-point dot com>]

On Mon, 1 Jul 2002, Gary Smith wrote:
> I did not specify the --prefix variable. I did set the srcdir and objdir in
> the configure file prior to running ./configure. srcdir=/usr/lib/gcc-3.1,
> objdir=/usr/lib/gcc3.1-lib.  This is all I configured away from the default.

Changing srcdir, objdir isn't part of the typical GCC installation, and
shouldn't be needed; what document(s) advised you to do this?

Setting --prefix is important if you want to install somewhere besides
/usr/local.  Please see http://gcc.gnu.org/install/ for detailed
installation notes.

> Does 2.96 have problems?

I don't know.  2.96 isn't an FSF release.  It was produced by Red Hat
solely for use on their own GNU/Linux distribution.  You might check with
Red Hat for bugs reported on 2.96, or availability of package updates.

> I will check /usr/local/bin/gcc,  but what am I looking for?

Assuming you successfully built & installed gcc into /usr/local, you could
enter:

[jsturm@suzy jsturm]$ /usr/local/bin/gcc -v

and see something similar to:

Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../configure --enable-languages=c++,java
--enable-threads : (reconfigured)
Thread model: posix
gcc version 3.1 20020426 (prerelease)

> How do I get the system to recognise it has another compiler to look for?

It depends on your OS and the package you're building.  It would be better
to ask the maintainers of those; this list is about _developing_ GCC not
_using_ it.  That said, as a general bit of advice either or both of the
following commands may help:

export PATH=/usr/local/bin:$PATH
export CC=/usr/local/bin/gcc

Jeff