gcc 2.95.x

Declan Moriarty junk_mail at iol.ie
Fri Aug 26 07:48:39 PDT 2005


Recently, Somebody Somewhere wrote these words
> Hi,
> 
> I need to install libstdc++.so.5 on my LFS system
> (6.0-testing-20040901). Unfortunately this gcc version was removed
> from the blfs book so I tried the instructions from blfs 5.0. I added
> another patch for the trap posix incompatibility but when compiling it
> stops with the following error:
> 
> ----------------- snip -------------------------- make[2]: Entering
> directory `/srv/sources/gcc-2-build/i686-pc-linux-gnu/libio' if [
> x"yes" = xyes ] && [ ! -d pic ]; then \ mkdir pic; \ else true; fi
> touch stamp-picdir test x"yes" != xyes ||\
> /srv/sources/gcc-2-build/gcc/xgcc -B/srv/sources/gcc-2-build/gcc/
> -B/opt/gcc-2.95.3/i686-pc-linux-gnu/bin/ -c -O2 -I.
> -I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO -fpic
> ../../../gcc-2.95.3/libio/iogetline.c -o pic/iogetline.o In file
> included from ../../../gcc-2.95.3/libio/libio.h:167, from
> ../../../gcc-2.95.3/libio/iolibio.h:1, from
> ../../../gcc-2.95.3/libio/libioP.h:47, from
> ../../../gcc-2.95.3/libio/iogetline.c:26:
> /usr/include/bits/stdio-lock.h:24: lowlevellock.h: Datei oder
> Verzeichnis nicht gefunden make[2]: *** [iogetline.o] Fehler 1
> make[2]: Leaving directory
> `/srv/sources/gcc-2-build/i686-pc-linux-gnu/libio' make[1]: ***
> [all-target-libio] Fehler 2 make[1]: Leaving directory
> `/srv/sources/gcc-2-build' make: *** [bootstrap] Fehler 2
> ----------------- snip --------------------------
> 
> Why the hell does /usr/include/bits/stdio-lock.h include a file
> lowlevellock.h and can not find it?  Has anyone tips for installing
> gcc 2.95.x into /opt on a linux-2.6-gcc-3.4.1-glibc-2.3.4-system?
> 
> Thanx for your help, Dan



You might need gcc-2.95 to make gcc-2.95 :-/.

If you just want libstdc++.so.5, do you want it attached to an email?

Have you installed Openoffice? You may have libstdc++.so.5 in the 
OO/program directory. I don't know if that's been suggested.
-- 

	With best Regards,


	Declan Moriarty.



More information about the blfs-support mailing list