Le Thu, 5 May 2005 21:23:05 +0600 "Alexander E. Patrakov"
<[EMAIL PROTECTED]> a �crit :

> Matthias B. wrote:
> 
> > On Wed, 4 May 2005 22:26:41 +0100 (BST) Ken Moffat
> > <[EMAIL PROTECTED]> wrote:
> > 
> >>  Worst case, I guess you might have to build a 3.3 gcc (3.3.4 or
3.3.5)
> >> and use that to build 2.95.3.
> > 
> > It's worse than that. The C++ components of gcc 2.95 don't compile
with
> > recent glibcs.
> 
> That's just FUD.
> 
>
http://www.diy-linux.org/pipermail/diy-linux-dev/2005-January/000285.html

Compilation now goes well until I get this error message :

make[2]: Entering directory `/sources/gcc-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 ||\
  /sources/gcc-build/gcc/xgcc -B/sources/gcc-build/gcc/
-B/opt/gcc-2.95.3/i686-pc-linux-gnu/bin/ -c -g -O2 -I.
-I../../../gcc-2.95.3/libio -D_IO_MTSAFE_IO -I/tmp/foo/usr/include -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: Aucun fichier ou
r?pertoire de ce type make[2]: *** [iogetline.o] Erreur 1
make[2]: Leaving directory `/sources/gcc-build/i686-pc-linux-gnu/libio'
make[1]: *** [all-target-libio] Erreur 2
make[1]: Leaving directory `/sources/gcc-build'
make: *** [bootstrap] Erreur 2

I saw a message somewhere about lowlevellock.h. I'll try to find it again
:()

I definitly need a tool to collect notes rapidly from my readings and
browsing. Do you have one that suits my wills ?

\bye

-- 

Nicolas FRANCOIS
http://nicolas.francois.free.fr

We are the Micro$oft.
Resistance is futile.
You will be assimilated.
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to