David Berry schreef:
> Hello,
>
> I am getting an error in 6.12 GCC-4.1.1-Cross Compiler Final during
> the build.
> Build output
> ...
> checking for i686-pc-linux-uclibc-gcc...
> /home/clfs/gcc-build/./gcc/xgcc -B/home/clfs/gcc-build/./gcc/
> -B/sandboxes/lfs-router/clfs/cross-tools/i686-pc-linux-uclibc/bin/
> -B/sandboxes/lfs-router/clfs/cross-tools/i686-pc-linux-uclibc/lib/
> -isystem
> /sandboxes/lfs-router/clfs/cross-tools/i686-pc-linux-uclibc/include
> -isystem
> /sandboxes/lfs-router/clfs/cross-tools/i686-pc-linux-uclibc/sys-include
> checking for C compiler default output file name... configure: error:
> C compiler cannot create executables
> See `config.log' for more details.
> make[1]: *** [configure-target-libmudflap] Error 1
> make[1]: Leaving directory `/home/clfs/gcc-build'
> make: *** [all] Error 2
>
> I have received a similar error in a previous build effort (different
> project) when the selected compiler is incorrect/does not exist.  That
> was solved setting path etc to find the correct compiler.
>
> Checking the configure log of ./gcc/config.log (which has completed
> building) I find:
> configure:1308: creating cache ./config.cache
> configure:1426: checking build system type
> configure:1444: result: x86_64-cross-linux-gnu
> configure:1452: checking host system type
> configure:1466: result: x86_64-cross-linux-gnu
> configure:1474: checking target system type
> configure:1488: result: i686-pc-linux-uclibc
> configure:1559: checking LIBRARY_PATH variable
>
> checking the configure log of ./i686-pc-linux-uclibc/libmudflap/ I find:
> configure:1231: creating cache ./config.cache
> configure:1351: checking build system type
> configure:1369: result: x86_64-cross-linux-gnu
> configure:1377: checking host system type
> configure:1391: result: i686-pc-linux-uclibc
> configure:1399: checking target system type
> configure:1413: result: i686-pc-linux-uclibc
>
> The line "checking host system type" comes back with a different
> answer in the
> build for libmudflap vs gcc  ...
>
> My next guess is that it is now trying to use the compiler which was
> previouslycreated during
> 6.8.1 Installation of Cross GCC Compiler with Static libgcc and no
> Threads
>
> Any other ideas, suggestions to try?
>
> Version of the book I am following ... SVN-0.0.1-20061204
> Environment variables:
> [EMAIL PROTECTED] ~/gcc-build $ echo $BUILD
> -m32
> [EMAIL PROTECTED] ~/gcc-build $ echo $CLFS_HOST
> x86_64-cross-linux-gnu
> [EMAIL PROTECTED] ~/gcc-build $ echo $CLFS_TARGET
> i686-pc-linux-uclibc
>
> I have attempted to follow the book as closely as possible.
> I have started over once and arrived back at the same point.
>
> Some other concerns:
> During the build of uClibc make defconfig results in a .config file
> with a target set to x86_64.
> During the build of uClibc the commands to remove certain directories
> did not result in deleting anything:
> rm include/{asm,asm-generic,linux}
> rm: cannot remove `include/asm': No such file or directory
> rm: cannot remove `include/asm-generic': No such file or directory
> rm: cannot remove `include/linux': No such file or directory
>
>
> Thanks,
> Dave
CLFS embedded is a bit outdated, recently there have been some changes
in uclibc that resulted in breaking the uclibc config, try make
defconfig TARGET=target_arch instead of that sed command, the rm command
is no longer needed, that warning can be ignored. It seems your final
GCC misses --host $CLFS_TARGET in ./configure.
 If I were you, I would configure the uclibc manually with make
menuconfig after make defconfig and the sed's, to make sure uclibc
config is correct with respect to arch and cpu configuration.

Maarten
_______________________________________________
Clfs-support mailing list
Clfs-support@lists.cross-lfs.org
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

Reply via email to