<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV> </DIV>
<DIV>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.    </DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>Tom  </DIV>
<DIV> </DIV>
<DIV><BR>--- On <B>Thu, 7/8/10, Lance Jump <I><lancej29@gmail.com></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Lance Jump <lancej29@gmail.com><BR>Subject: [Clfs-support] CLFS for ARM/OpenRD/Plugcomputer<BR>To: clfs-support@lists.cross-lfs.org<BR>Date: Thursday, July 8, 2010, 9:26 AM<BR><BR>
<DIV id=yiv359656648>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.<BR><BR>Before I describe the latest problem, let me first ask if I am following the best route. I am following:<BR>
<H4 style="FONT-WEIGHT: normal">Cross-Compiled Linux From Scratch - Sysroot - Version SVN-0.0.1-20090726-ARM</H4>Is there something else I should be using? If so, I'll start from there and get back when/if I have a problem.<BR><BR>The specific problem I am having with the above is building gcc final (5.12). It fails as follows:<BR>..............<BR>checking for arm-unknown-linux-gnu-strip... /mnt/clfs/cross-tools/arm-unknown-linux-gnu/bin/strip<BR>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<BR>checking for C compiler default output file name... configure: error: in `/mnt/clfs/work/gcc-build/arm-unknown-linux-gnu/libgomp':<BR>configure: error: C compiler cannot
 create executables<BR>See `config.log' for more details.<BR>make[1]: *** [configure-target-libgomp] Error 1<BR>make[1]: Leaving directory `/mnt/clfs/work/gcc-build'<BR>make: *** [all] Error 2<BR>...............<BR><BR>Looking at config.log from libgomp I find:<BR><BR>...............<BR>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<BR>xgcc: '-V' must come at the start of the command line<BR>configure:2546: $? = 1<BR>configure:2569: checking for C compiler default output file name<BR>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<BR>/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<BR>configure:2575: $? = 1<BR>configure: failed program was:<BR>| /* confdefs.h.  */<BR>......................<BR><BR>This is exactly the same symptom posted in at least two other threads, but I can't find a <FONT size=2>solution. One looked like it had a solution by giving this link:<BR></FONT><BR><A href="http://archives.free.net.ph/message/20091005.172315.9c92afe5.ca.html" target=_blank rel=nofollow>http://archives.free.net.ph/message/20091005.172315.9c92afe5.ca.html</A><BR><BR>but that server appears to be down.<BR><BR>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.<BR><BR>Any help/advice will be appreciated.<BR></DIV><BR>-----Inline Attachment Follows-----<BR><BR>
<DIV class=plainMail>_______________________________________________<BR>Clfs-support mailing list<BR><A href="http://us.mc569.mail.yahoo.com/mc/compose?to=Clfs-support@lists.cross-lfs.org" ymailto="mailto:Clfs-support@lists.cross-lfs.org">Clfs-support@lists.cross-lfs.org</A><BR><A href="http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org" target=_blank>http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org</A><BR></DIV></BLOCKQUOTE></td></tr></table><br>