This is the mail archive of the
mailing list for the GCC project.
GCC 3.1 on Mandrake 8.1: successful build
- From: David Shepperton <dshepperton at yahoo dot com>
- To: gcc at gcc dot gnu dot org
- Date: Sun, 2 Jun 2002 22:18:07 -0700 (PDT)
- Subject: GCC 3.1 on Mandrake 8.1: successful build
GCC 3.1 on Mandrake 8.1: successful build (using
System is an Athlon 1400MHz, 512MB RAM, 40GB HD ULTRA
ATA 100 HD
gcc -v output:
Reading specs from
Thread model: single
gcc version 3.1
GNU/Linux specific info:
Mandrake Linux release 8.1 (Vitamin) for i586
Kernel 2.4.8-26mdk on an i686 / \l
uname -a/--version output:
Linux shep 2.4.8-26mdk #1 Sun Sep 23 17:06:39 CEST
2001 i686 unknown
uname (GNU sh-utils) 2.0.11
rpm -q glibc output:
I use GCC for compiling C/C++ programs only, so that
is all the testing I have done so far.
As reported by Theirry Felt (in
had to manually adjust the links that the Mandrake
installation had for gcc/g++ (located in /usr/bin) to
point to the new (normal) location for gcc/g++. I
imagine I would have had to do the same for the links
for other gcc-supported language compilers if I wanted
to use them (Mandrake 8.1 by default gives an
additional layer of indirection: for example, the
original link to g++ was /usr/bin/g++ ->
/etc/alternative/g++ -> /usr/bin/g++-2.96).
Also, the only programs I tried to run after compiling
them with gcc 3.1 (C++ programs) would initially fail
with the message:
[shep@shep cpp]$ ./prog
./prog: error while loading shared libraries:
libstdc++.so.4: cannot open shared object file: No
such file or directory
I presume there is an environment variable for this or
something, but I don't know what it is; so I copied
the link to libstdc++.so.4 from /usr/local/lib to
/usr/lib, which made things run fine.
Thanks for all your good work, GCC team!
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup