Quote:
|
Originally Posted by mwette
I would say the best way to do this is to download the sources and build
from scratch. I believe the "configure" script accepts an argument to add
a prefix/suffix to commands so that gcc could be installed as something
like gcc296.
|
I found this rpm:
compat-gcc-296-2.96-138.src.rpm
and it generated
compat-gcc-296-debuginfo-2.96-138.i386.rpm
compat-libgcc-296-2.96-138.i386.rpm
compat-libstdc++-296-2.96-138.i386.rpm
$ rpm -qlp compat-gcc-296-debuginfo-2.96-138.i386.rpm
/usr/lib/debug/usr/lib/libstdc++-3-libc6.2-2-2.10.0.so.debug
$ rpm -qlp compat-libgcc-296-2.96-138.i386.rpm
/usr/lib/gcc-lib
/usr/lib/gcc-lib/i386-redhat-linux
/usr/lib/gcc-lib/i386-redhat-linux/2.96
/usr/lib/gcc-lib/i386-redhat-linux/2.96/crtbegin.o
/usr/lib/gcc-lib/i386-redhat-linux/2.96/crtbeginS.o
/usr/lib/gcc-lib/i386-redhat-linux/2.96/crtend.o
/usr/lib/gcc-lib/i386-redhat-linux/2.96/crtendS.o
/usr/lib/gcc-lib/i386-redhat-linux/2.96/libgcc.a
/usr/lib/gcc-lib/i386-redhat-linux/2.96/libgcc_eh.a
$ rpm -qlp compat-libstdc++-296-2.96-138.i386.rpm
/usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
/usr/lib/libstdc++-libc6.2-2.so.3
Is this right?