[uClibc]parse error

[Erik Andersen]

On Thu Aug 03, 2000 at 11:53:12PM +0200, Denis Ducamp wrote:
> On Thu, Aug 03, 2000 at 12:26:18PM -0600, Erik Andersen wrote:
> > 
> > Sorry about the delay -- I got swamped and sortof neglected my
> > inbox for a bit.   I just placed a tarball with a snapshot of
> > CVS on 
> >     ftp://uclibc.org/
> 
> Tried the cvs version a few days ago and that snapshot now but I have the
> same errors :
> 
> uC-libc$ make
> if [ ! -L "include/asm" ]; then ln -s /usr/src/linux/include/asm include/asm ; fi
> if [ ! -L "include/net" ]; then ln -s /usr/src/linux/include/net include/net ; fi
> if [ ! -L "include/linux" ]; then ln -s /usr/src/linux/include/linux include/linux ; fi
> make -C error
> cc1: Invalid option -fdata-sections'
> make[1]: Entering directory /usr/local/src/uC-libc/error'
> gcc  -Os -fno-builtin -nostdinc  -Dlinux -D__linux__ -I../include -I/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/include -I. -D__PIC__ -D__LIBC__  -Wall  -D__PIC__    -c error.c -o error.o
> In file included from error.c:5:
> ../include/string.h:13: parse error before _dest'
> ../include/string.h:16: parse error before _dest'
> ../include/string.h:20: parse error before _dest'
> ../include/string.h:23: parse error before _dest'
> ../include/string.h:41: parse error before _dest'
> ../include/string.h:79: parse error before _stringp'
> ../include/string.h:84: parse error before _s'
> In file included from error.c:6:
> ../include/stdlib.h:73: parse error before _name'
> make[1]: *** [error.o] Error 1
> make[1]: Leaving directory /usr/local/src/uC-libc/error'
> make: *** [error] Error 2
> 
> With make -i I have such parse errors in directories error, getent,
> malloc-simple, misc, regex, stdio2, string, sysdeps/linux/i386,
> sysdeps/linux/common, termios, and time. Finally I get 186 .o files and a
> 144k libc.a
> 
> Is there something special to know/have ?
> 
> I have a slackware 7.0 (glibc-2.1.2 egcs-2.91.66).

Hmm.  That is very wierd.  I use Debian potato (gcc 2.95.2, glibc 2.1.3).
It works for me so far...  Hmmm.  Ok, it is choking on stuff that will 
only work with a newer gcc.

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--