glibc-2.3.2 (Chapter 5) is confused by earlier errors

Greg Schafer gschafer at zip.com.au
Sun Nov 16 02:29:51 PST 2003


On Sun, Nov 16, 2003 at 08:21:37AM +0000, Brett wrote:
> sorry about that. I hope this contains the required information:
> 
> ----------------
> 
> mkdir /home/lfs/glibc-build/gnu
> mkdir /home/lfs/glibc-build/csu
> In file included from version.c:33:
> /home/lfs/glibc-build/csu/version-info.h:1:1: missing terminating "
>    character
> /home/lfs/glibc-build/csu/version-info.h:2:1: missing terminating "
>    character
> /home/lfs/glibc-build/csu/version-info.h:3:1: missing terminating "
>    character
> /home/lfs/glibc-build/csu/version-info.h:4:1: missing terminating "
>    character
> In file included from ../include/pthread.h:1,
>                  from
> ../linuxthreads/sysdeps/pthread/bits/libc-lock.h:23,
>                  from ../sysdeps/generic/ldsodefs.h:38,
>                  from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
>                  from ../sysdeps/unix/sysv/linux/init-first.c:30:
> ../linuxthreads/sysdeps/pthread/pthread.h:163: error: parse error
>    before "__thread"

It looks like you erroneously applied the GCC "No-Fixincludes" patch in the
first pass of GCC when the book clearly states only apply it in the second
pass. In other words, you might have made a boo-boo. You're not very far in,
so best bet is wipe everything and start again from scratch.



More information about the lfs-support mailing list