gschafer at zip.com.au
Thu Jan 8 02:34:34 PST 2004
On Thu, Jan 08, 2004 at 05:24:30PM +0800, tgarnsey at swiftdsl.com.au wrote:
> I've been having trouble with the very first gcc compilation in chapter
> five (LFS v5.0) on an Athlon 64. Not sure if this architecture has
> anything to do with the problem, but I did notice some posts implying not
> many people had tried LFS on it yet, and their might be some problems.
Athlon 64 is so new that it hasn't received wide LFS testing yet. So
unfortunately that means you're pretty much on your own :-(
> -fno-asynchronous-unwind-tables \
> -c ../../gcc-3.3.1/gcc/crtstuff.c -DCRT_BEGIN \
> -o crtbegin.o
> In file included from ../../gcc-3.3.1/gcc/crtstuff.c:62:
> ../../gcc-3.3.1/gcc/tsystem.h:72:19: stdio.h: No such file or directory
> ../../gcc-3.3.1/gcc/tsystem.h:75:23: sys/types.h: No such file or directory
> ../../gcc-3.3.1/gcc/tsystem.h:78:19: errno.h: No such file or directory
> ../../gcc-3.3.1/gcc/tsystem.h:85:20: string.h: No such file or directory
> ../../gcc-3.3.1/gcc/tsystem.h:89:20: stdlib.h: No such file or directory
> ../../gcc-3.3.1/gcc/tsystem.h:90:20: unistd.h: No such file or directory
There is the source of the problem. For some reason, the bootstrap compiler
(i.e. the compiler on the host) cannot find these basic headers which come
with the host's Glibc. I'm assuming the initial compile of binutils went ok?
If so, then I don't understand the problem at all.
More information about the lfs-support