I've built the 1.1.0 release for the PowerPC sucessfully. My experience building from the CLFS WIP version has always been it's kind of iffy. So, my suggestion is to try to adapt the 1.1.0 CLFS release to build for ARM. I'm not sure how difficult it is to modify it for ARM but I think you will have a better chance at success starting with the 1.1.0 release as a baseline. Tom
--- On Thu, 7/8/10, Lance Jump <[email protected]> wrote: From: Lance Jump <[email protected]> Subject: [Clfs-support] CLFS for ARM/OpenRD/Plugcomputer To: [email protected] Date: Thursday, July 8, 2010, 9:26 AM I am trying to build a CLFS system for a Marvell/ARM system and have made several attempts over the past weeks with no success. I tried CLFS-arm-embedded and failed, then tried to modify CLFS-powerPC and failed and now I am trying CLFS-arm-sysroot with no success. Before I describe the latest problem, let me first ask if I am following the best route. I am following: Cross-Compiled Linux From Scratch - Sysroot - Version SVN-0.0.1-20090726-ARMIs there something else I should be using? If so, I'll start from there and get back when/if I have a problem. The specific problem I am having with the above is building gcc final (5.12). It fails as follows: .............. checking for arm-unknown-linux-gnu-strip... /mnt/clfs/cross-tools/arm-unknown-linux-gnu/bin/strip checking for arm-unknown-linux-gnu-gcc... /mnt/clfs/work/gcc-build/./gcc/xgcc -B/mnt/clfs/work/gcc-build/./gcc/ -B/mnt/clfs/cross-tools/arm-unknown-linux-gnu/bin/ -B/mnt/clfs/cross-tools/arm-unknown-linux-gnu/lib/ -isystem /mnt/clfs/cross-tools/arm-unknown-linux-gnu/include -isystem /mnt/clfs/cross-tools/arm-unknown-linux-gnu/sys-include checking for C compiler default output file name... configure: error: in `/mnt/clfs/work/gcc-build/arm-unknown-linux-gnu/libgomp': configure: error: C compiler cannot create executables See `config.log' for more details. make[1]: *** [configure-target-libgomp] Error 1 make[1]: Leaving directory `/mnt/clfs/work/gcc-build' make: *** [all] Error 2 ............... Looking at config.log from libgomp I find: ............... configure:2543: /mnt/clfs/work/gcc-build/./gcc/xgcc -B/mnt/clfs/work/gcc-build/./gcc/ -B/mnt/clfs/cross-tools/arm-unknown-linux-gnu/bin/ -B/mnt/clfs/cross-tools/arm-unknown-linux-gnu/lib/ -isystem /mnt/clfs/cross-tools/arm-unknown-linux-gnu/include -isystem /mnt/clfs/cross-tools/arm-unknown-linux-gnu/sys-include -V </dev/null >&5 xgcc: '-V' must come at the start of the command line configure:2546: $? = 1 configure:2569: checking for C compiler default output file name configure:2572: /mnt/clfs/work/gcc-build/./gcc/xgcc -B/mnt/clfs/work/gcc-build/./gcc/ -B/mnt/clfs/cross-tools/arm-unknown-linux-gnu/bin/ -B/mnt/clfs/cross-tools/arm-unknown-linux-gnu/lib/ -isystem /mnt/clfs/cross-tools/arm-unknown-linux-gnu/include -isystem /mnt/clfs/cross-tools/arm-unknown-linux-gnu/sys-include -g -O2 conftest.c >&5 /mnt/clfs/work/gcc-build/./gcc/cc1: error while loading shared libraries: /mnt/clfs/work/gcc-build/./gcc/libgcc_s.so.1: ELF file OS ABI invalid configure:2575: $? = 1 configure: failed program was: | /* confdefs.h. */ ...................... This is exactly the same symptom posted in at least two other threads, but I can't find a solution. One looked like it had a solution by giving this link: http://archives.free.net.ph/message/20091005.172315.9c92afe5.ca.html but that server appears to be down. I am not a complete Linux noob (although I am new to CLFS) having successfully built an LFS system for an embedded x86 about a year ago. Still I am no expert on the tool building process. Any help/advice will be appreciated. -----Inline Attachment Follows----- _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
_______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
