gcc 3.2.3 (Linux)

gcc 3.2.3 (Linux)

[Piotr Gogolewski]

Hi.
Another sucessful build:

i686-pc-linux-gnu
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs
Configured with: ../../src/gcc-3.2.3/configure --prefix=/usr --with-gnu-as
 --enable-threads --with-system-zlib
Thread model: posix
gcc version 3.2.3

Compiled with:
make -j 2 CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2
 -fno-implicit-templates' bootstrap

System:
kernel 2.4.20 SMP
glibc 2.1.3
binutils 2.11.2
previous gcc version: 2.95.3
Some time ago it was Red Hat 5.1, all upgrades were made from tarballs.

One thing I had to figure out by myself (or I didn't carefully read
documantation... ) was:
cd /lib && rm cpp && ln -s ../usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/tradcpp0 cpp
instead of:
cd /lib && rm cpp && ln -s ../usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/cpp0 cpp
(as in previous version).

Thanks for great software. :-)
-- 
Pozdrawiam, Piotr Gogolewski.
+-{ Serwis "Docent OnLine" http://www.chemia.px.pl }------------------+
+-{ klucz PGP & Geek Code: mail docent@panoramix.net.pl -s"get pgp" }-+

Re: gcc 3.2.3 (Linux)

[Alexandre Oliva]

On Aug  3, 2003, Piotr Gogolewski <docent@panoramix.net.pl> wrote:

> One thing I had to figure out by myself (or I didn't carefully read
> documantation... ) was:
> cd /lib && rm cpp && ln -s ../usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/tradcpp0 cpp

Any reason to not use ../usr/bin/cpp instead of the traditional
preprocessor?  There wasn't a cpp driver back in 2.95, IIRC, so
/lib/cpp used to be linked to an internal program.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

Re: gcc 3.2.3 (Linux)

[Zack Weinberg]

Alexandre Oliva <aoliva@redhat.com> writes:

> On Aug  3, 2003, Piotr Gogolewski <docent@panoramix.net.pl> wrote:
>
>> One thing I had to figure out by myself (or I didn't carefully read
>> documantation... ) was:
>> cd /lib && rm cpp && ln -s ../usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/tradcpp0 cpp
>
> Any reason to not use ../usr/bin/cpp instead of the traditional
> preprocessor?  There wasn't a cpp driver back in 2.95, IIRC, so
> /lib/cpp used to be linked to an internal program.

Indeed, and in 3.3 that internal program vanishes entirely, you must
refer to /usr/bin/cpp.

(I would in fact suggest not having /lib/cpp at all, odds are nothing
will break.)

zw

Re: gcc 3.2.3 (Linux)

[Paul Jarc]

"Zack Weinberg" <zack@codesourcery.com> wrote:
> (I would in fact suggest not having /lib/cpp at all, odds are nothing
> will break.)

Imake will, IIRC, but it can be fixed by setting $IMAKECPP.  A couple
of other tweaks would also be needed to build XFree86; I think the
path to cpp gets compiled into xrdb.


paul