From mboxrd@z Thu Jan  1 00:00:00 1970
From: tjb@starbase.neosoft.com (Timothy J. Bogart)
To: help-gcc@gnu.org
Subject: Re: Do you need an existing compiler to install gcc?
Date: Fri, 31 Dec 1999 22:24:00 -0000
Message-ID: <33106DF648E7AE93.D1A40303C488412F.4DDA83F433F0FF30@lp.airnews.net>
References: <83rkev$bh1$1@nnrp1.deja.com>
X-SW-Source: 1999-12n/msg00320.html
Message-ID: <19991231222400.GDzUVPcPxgUVfkCyPumSAQ8U4iK6s-WE8sQgvg852hs@z>

If you are going to configure and build the gcc compiler, you
need a working compiler to do this.  Presuming you are using
the default ksh, you will want to make sure the working compiler
is in your path.  Doing an

export CC=<path-to-working-compiler>/compiler

will help.  This working compiler can be a download of gcc
from BULL, for example, but you must have _some_ compiler if
you are to build code.  You will need root permissions to
put the BULL compiler, or anybody else who has built gcc
to go in the default place.../usr/local/bin.  Hence the above
becomes

export CC=/usr/local/bin/gcc

if you did this.


Plus you migh double check the instructions...from memory, I 
seem to recall that they recommend you not do the configure/build
in the 'home' of what you undar, but create another directory and
do it from there...

Hope that helps some.

In article < 83rkev$bh1$1@nnrp1.deja.com >,  <adezoysa@my-deja.com> wrote:
>I have a rs6000 with 4.3.1.0, downloaded gcc-2.95.2, unzipped and
>expanded it.  When i go to configure it, it tells me :
>
># /us3/temp/gcc-2.95.2/configure
>Configuring for a powerpc-ibm-aix4.3.1.0 host.
>Created "Makefile" in /us3/temp/source using "mh-frag"
>/us3/temp/gcc-2.95.2/configure[1462]: /us3/temp/gcc-2.95.2/gcc: 0403-
>006 Execut.
>*** The command '/us3/temp/gcc-2.95.2/gcc -o conftest -O2   conftest.c'
>failed.
>*** You must set the environment variable CC to a working compiler.
>
>Whats going on?  Do I need an existing CC compiler prior to this?
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.