2006/7/16, Jim Gifford <[EMAIL PROTECTED]>: > Jonathan Davis wrote: > > I am trying to create a CLFS x86_64 multilib system from SuSE 10.1 which > > is also 64 bit. I'm using CLFS Version 1.0.0rc1-x86_64-Multilib. > > Following the instructions, I get the following error message when > > running "configure" in 5.6 (Cross Binutils-2.17): > > > > configure: warning: x86_64-suse-linux: invalid host type > > configure: warning: |: invalid host type > > configure: error: can only configure for one host and one target at a time > > > > I assume that it just doesn't like my host triplet. If > > > > 1. I do not give configure the host, but just the target, or if > > 2. I set both the host and the target to the target > > (x86_64-unknown-linux-gnu), or if > > 3. I give it neither the host nor the target, > > > > then I am able to continue. GCC's "configure" in the next section > > reacts the same way. However, even if I make the "configure" happy by > > one of the three ways above, "make all-gcc" gives me this at the end of > > its build: > > > > > > In file included from ../../gcc-4.1.1/gcc/crtstuff.c:68: > > ../../gcc-4.1.1/gcc/tsystem.h:90:19: error: stdio.h: No such file or > > directory > > ../../gcc-4.1.1/gcc/tsystem.h:93:23: error: sys/types.h: No such file or > > directory > > ../../gcc-4.1.1/gcc/tsystem.h:96:19: error: errno.h: No such file or > > directory > > ../../gcc-4.1.1/gcc/tsystem.h:103:20: error: string.h: No such file or > > directory > > ../../gcc-4.1.1/gcc/tsystem.h:104:20: error: stdlib.h: No such file or > > directory > > ../../gcc-4.1.1/gcc/tsystem.h:105:20: error: unistd.h: No such file or > > directory > > In file included from > > /mnt/lfs/sources/gcc-build/./gcc/include/syslimits.h:7, > > from /mnt/lfs/sources/gcc-build/./gcc/include/limits.h:11, > > from ../../gcc-4.1.1/gcc/tsystem.h:108, > > from ../../gcc-4.1.1/gcc/crtstuff.c:68: > > /mnt/lfs/sources/gcc-build/./gcc/include/limits.h:122:61: error: > > limits.h: No such file or directory > > In file included from ../../gcc-4.1.1/gcc/crtstuff.c:68: > > ../../gcc-4.1.1/gcc/tsystem.h:111:18: error: time.h: No such file or > > directory > > make[1]: *** [crtbegin.o] Error 1 > > make[1]: Leaving directory `/mnt/lfs/sources/gcc-build/gcc' > > make: *** [all-gcc] Error 2 > > > > I have not been able to find a way to make it happy. I would assume > > that it's a path problem somewhere - especially given that a library as > > important as stdio.h is among the missing - but I don't know. > > > > So, my host distribution is 64-bit SuSE Linux 10.1 with a triplet of > > x86_64-suse-linux. > > The target is the same machine with the triplet x86_64-unknown-linux-gnu. > > I am using CLFS 1.0.0rc1-x86_64-Multilib. > > > > > > I would guess that the problem lies with binutils, but it could just as > > easily be gcc given that it's gcc's build that fails. > > Any suggestions on what the problem could be and particulary on how to > > fix it would be appreciated. I have not been able to hunt down anything > > useful with regards to this problem. > > > > - Jonathan Davis > > > > _______________________________________________ > > Clfs-support mailing list > > [email protected] > > http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support > > > Suse always has to be different don't they. > > Changed your CLFS_HOST to use > $(echo ${MACHTYPE} | sed -e 's/unknown/cross/g' -e 's/-pc-/-cross-/g' -e > 's/-suse-/-cross-/g' > or set it manually to > > x86_64-cross-linux-gnu > > > _______________________________________________ > Clfs-support mailing list > [email protected] > http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support >
Thanks! I'm finally able to get through gcc's first install and continue on my way. Obviously SuSE is not following the conventions that CLFS expects. However, given that the x86_64 convention seems to be to put "unknown" in the middle of the triplet, it seemed perfectly logical to me for SuSE to have put 'suse" there since then it WAS known. Perhaps a little more explanation in the book would be in order. I don't know if any other distributions do something similar or not, but if many do, then it certainly would be a good idea to put a short note about what the host name SHOULD look like after the sed command. If it's only SuSE, then it's probably fine though. Anyway, thanks for the help. - Jonathan Davis _______________________________________________ Clfs-support mailing list [email protected] http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support
