This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Successful install V3.2 on True64 v5.1
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Karl dot Simonard at support-externe dot space dot alcatel dot fr
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 11 Sep 2002 09:20:49 -0700
- Subject: Re: Successful install V3.2 on True64 v5.1
- References: <C1256C31.004D907A.00@vzmta01.netfr.alcatel.fr>
On Wed, Sep 11, 2002 at 03:57:38PM +0200, Karl.Simonard@support-externe.space.alcatel.fr wrote:
>
>
> After a lot of problems, this is my solution to install GCC v3.2
> Server : DS20
> O.S. : OSF1 V5.1
> Initial state: gcc v3.0.3.
>
> # cd /freeware/gcc/gcc3.2
> # mkdir test
> # cd test
> # Configure with CC="gcc -Wa,-oldas" ../configure - -enable-languages=c,c++,f77
> - -prefix=/freeware/gcc/v3.2
> # cp ../gcc.intl/plural* gcc/intl
> # make
> # cp ../install-sh .
> # make install
The GCC 3.2 installation instructions say "we highly recommend that GCC
be built into a separate directory than the sources which does not
reside within the source tree." For the 3.3 prerelease, building in the
source directory, or a subdirectory of the source directory, is not
supported at all. You might not have run into problems if you had built
in a separate directory as recommended by the installation instructions.
It's also highly recommended to use "make bootstrap" rather than a
simple "make". It takes long but is safer and can detect serious
problems.
Janis