well before start let me introduce my env variables:<br>export CLFS="/opt/arm-linux/arm-linux-gnueabi"<br>export CLFS_CROSSTOOLS="/opt/arm-linux/bin" <br>export CLFS_HOST="i686-pc-linux-gnu"<br>
export CLFS_TARGET="arm-linux-gnueabi"<br><br>well my binutils 2.18 compiled but, with different arguments not exactly like the book, I used the following:<br>AR=ar AS=as ../../sources/binutils-2.18/configure --prefix=/opt/arm-linux --target=${CLFS_TARGET} --enable-shared --host=i686
<br><br>I don't know why, but was the only way to it configure and compilate, after this I did the glibc-headers install,gcc-static, glibc-arm and now I stoped in the gcc-arm (chapter 5.9), I used the default compilation line in the book and get the following result after make:
<br><br>hecking whether stripping libraries is possible... yes<br>checking dynamic linker characteristics... GNU/Linux ld.so<br>checking command to parse /home/lvcargnini/puc/instramed/toolchain/build/gcc-arm/./gcc/nm output... failed
<br>checking if libtool supports shared libraries... yes<br>checking whether to build shared libraries... yes<br>checking whether to build static libraries... yes<br>appending configuration tag "CXX" to libtool
<br>
checking for exception model to use... call frame<br>checking for compiler with PCH support... no<br>checking for enabled PCH... no<br>checking for underlying I/O to use... stdio<br>checking for ANSI C header files... no
<br>
checking for sys/types.h... no<br>checking for sys/stat.h... no<br>checking for stdlib.h... no<br>checking for string.h... no<br>checking for memory.h... no<br>checking for strings.h... no<br>checking for inttypes.h... no
<br>checking for stdint.h... no<br>checking for unistd.h... no<br>checking for C locale to use... generic<br>checking for std::allocator base class... new<br>configure: "C" header strategy set to c_std<br>checking for enabled long long specializations... yes
<br>checking wchar.h usability... no<br>checking wchar.h presence... yes<br>configure: WARNING: wchar.h: present but cannot be compiled<br>configure: WARNING: wchar.h: check for missing prerequisite headers?<br>configure: WARNING:
wchar.h: see the Autoconf documentation<br>configure: WARNING: wchar.h: section "Present But Cannot Be Compiled"<br>configure: WARNING: wchar.h: proceeding with the preprocessor's result<br>configure: WARNING:
wchar.h: in the future, the compiler will take precedence<br>configure: WARNING: ## ----------------------------------------- ##<br>configure: WARNING: ## Report this to the package-unused lists. ##<br>configure: WARNING: ## ----------------------------------------- ##
<br>checking for wchar.h... yes<br>checking for mbstate_t... no<br>checking wctype.h usability... no<br>checking wctype.h presence... yes<br>configure: WARNING: wctype.h: present but cannot be compiled<br>configure: WARNING:
wctype.h: check for missing prerequisite headers?<br>configure: WARNING: wctype.h: see the Autoconf documentation<br>configure: WARNING: wctype.h: section "Present But Cannot Be Compiled"<br>configure: WARNING:
wctype.h: proceeding with the preprocessor's result<br>configure: WARNING: wctype.h: in the future, the compiler will take precedence<br>configure: WARNING: ## ----------------------------------------- ##<br>configure: WARNING: ## Report this to the package-unused lists. ##
<br>configure: WARNING: ## ----------------------------------------- ##<br>checking for wctype.h... yes<br>checking for enabled wchar_t specializations... no<br>checking for ISO C99 support in <math.h>... no<br>
checking complex.h usability... no<br>checking complex.h presence... yes<br>configure: WARNING: complex.h: present but cannot be compiled<br>configure: WARNING: complex.h: check for missing prerequisite headers?<br>configure: WARNING:
complex.h: see the Autoconf documentation<br>configure: WARNING: complex.h: section "Present But Cannot Be Compiled"<br>configure: WARNING: complex.h: proceeding with the preprocessor's result<br>configure: WARNING:
complex.h: in the future, the compiler will take precedence<br>configure: WARNING: ## ----------------------------------------- ##<br>configure: WARNING: ## Report this to the package-unused lists. ##<br>configure: WARNING: ## ----------------------------------------- ##
<br>checking for complex.h... yes<br>checking for ISO C99 support in <complex.h>... no<br>checking for ISO C99 support in <stdio.h>... no<br>checking for ISO C99 support in <stdlib.h>... no<br>checking for ISO C99 support in <
wchar.h>... no<br>checking for fully enabled ISO C99 support... no<br>configure: Debug build flags set to -g3 -O0<br>checking for additional debug build... no<br>checking for extra compiler flags for building... <br>checking for thread model used by GCC... posix
<br>checking for atomic builtins... no<br>checking for g++ that supports -ffunction-sections -fdata-sections... yes<br>checking nan.h usability... no<br>checking nan.h presence... no<br>checking for nan.h... no<br>checking
ieeefp.h usability... no<br>checking ieeefp.h presence... no<br>checking for ieeefp.h... no<br>checking endian.h usability... no<br>checking endian.h presence... yes<br>configure: WARNING: endian.h: present but cannot be compiled
<br>configure: WARNING: endian.h: check for missing prerequisite headers?<br>configure: WARNING: endian.h: see the Autoconf documentation<br>configure: WARNING: endian.h: section "Present But Cannot Be Compiled"
<br>configure: WARNING: endian.h: proceeding with the preprocessor's result<br>configure: WARNING: endian.h: in the future, the compiler will take precedence<br>configure: WARNING: ## ----------------------------------------- ##
<br>configure: WARNING: ## Report this to the package-unused lists. ##<br>configure: WARNING: ## ----------------------------------------- ##<br>checking for endian.h... yes<br>checking sys/isa_defs.h usability... no
<br>checking sys/isa_defs.h presence... no<br>checking for sys/isa_defs.h... no<br>checking machine/endian.h usability... no<br>checking machine/endian.h presence... no<br>checking for machine/endian.h... no<br>checking machine/param.h usability... no
<br>checking machine/param.h presence... no<br>checking for machine/param.h... no<br>checking sys/machine.h usability... no<br>checking sys/machine.h presence... no<br>checking for sys/machine.h... no<br>checking for sys/types.h... (cached) no
<br>checking fp.h usability... no<br>checking fp.h presence... no<br>checking for fp.h... no<br>checking float.h usability... no<br>checking float.h presence... yes<br>configure: WARNING: float.h: present but cannot be compiled
<br>configure: WARNING: float.h: check for missing prerequisite headers?<br>configure: WARNING: float.h: see the Autoconf documentation<br>configure: WARNING: float.h: section "Present But Cannot Be Compiled"
<br>configure: WARNING: float.h: proceeding with the preprocessor's result<br>configure: WARNING: float.h: in the future, the compiler will take precedence<br>configure: WARNING: ## ----------------------------------------- ##
<br>configure: WARNING: ## Report this to the package-unused lists. ##<br>configure: WARNING: ## ----------------------------------------- ##<br>checking for float.h... yes<br>checking for endian.h... (cached) yes
<br>checking for inttypes.h... (cached) no<br>checking locale.h usability... no<br>checking locale.h presence... yes<br>configure: WARNING: locale.h: present but cannot be compiled<br>configure: WARNING: locale.h: check for missing prerequisite headers?
<br>configure: WARNING: locale.h: see the Autoconf documentation<br>configure: WARNING: locale.h: section "Present But Cannot Be Compiled"<br>configure: WARNING: locale.h: proceeding with the preprocessor's result
<br>configure: WARNING: locale.h: in the future, the compiler will take precedence<br>configure: WARNING: ## ----------------------------------------- ##<br>configure: WARNING: ## Report this to the package-unused lists. ##
<br>configure: WARNING: ## ----------------------------------------- ##<br>checking for locale.h... yes<br>checking for float.h... (cached) yes<br>checking for stdint.h... (cached) no<br>checking for g++ that supports -ffunction-sections -fdata-sections... yes
<br>checking for ld version... 21800<br>checking for ld that supports -Wl,--gc-sections... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.<br>make[1]: *** [configure-target-libstdc++-v3] Error 1<br>
make[1]: Leaving directory `/home/lvcargnini/puc/instramed/toolchain/build/gcc-arm'<br>make: *** [all] Error 2<br><br><br>according your previous mail :<br>>2. I'm not familiar with the sysroot build, and you haven't made it
<br>easy for me by saying _which_ build of gcc this is. The final<br>options make it look like the compile in "installing system<br>software", but what is the '--enable-cross' and why do you need to<br>
pass '--with-headers' ?<br><br>this is an old parameter to set the path to include directory, just this<br><br>>3. You are installing this compiler into /opt/arm-linux : the<br>sysroot book puts the initial compilers into ${CLFS}/cross-tools and
<br>the final compiler into ${CLFS}/user. If /opt/arm-linux is the same<br>as ${CLFS} you are putting the compiler into the root of the system<br>tree.<br><br>take a look on my variables on beginning of message, in true I putting LFS inside /opt/arm-linux/arm-linux-gnueabi and cross-tools inside /opt/arm-linux (like crosstool, similar to denx too)
<br><br><br> >If all you are trying to do is build a cross-compiler for a kernel,<br>your prefix makes sense but you are overdoing things - no need for<br>c++ or posix threads: just follow the _principles_ in the _trunk_
<br>books (any of the 32-bit books, since we don't do arm there) :<br>headers, cross-binutils, cross-gcc-static - that's all.<br><br> >If you are trying to build a full system, messing around with the<br>prefix is very likely to break your build. The sysroot book lets you
<br>put ${CLFS} anywhere, so /opt/arm-linux is suitable if you have write<br>permission there (~/arm-linux is probably better for most people) but<br>you cannot go deviating from the book's structure (/opt-arm-linux<br>
instead of /opt/arm-linux/cross-tools or /opt/arm-linux/usr) and<br>expect it to just work.<br><br>I agree but my structure seems to be correct (is similar to Denx structure)<br><br><br><div class="gmail_quote">On Dec 26, 2007 7:11 PM, Ken Moffat <
<a href="mailto:zarniwhoop@ntlworld.com" target="_blank">zarniwhoop@ntlworld.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>
</div><div>On Wed, Dec 26, 2007 at 05:19:40PM -0200, Luís Vitório Cargnini wrote:<br>> well according to the book<br>> <a href="http://cross-lfs.org/view/clfs-sysroot/arm/cross-tools/binutils.html" target="_blank">
http://cross-lfs.org/view/clfs-sysroot/arm/cross-tools/binutils.html</a>:<br>> this is the result after make:<br>> && mv BLD-POTFILES-t BLD-POTFILES )<br>> cd .. \<br>> && CONFIG_FILES=po/Makefile.in:po/Make-in \
<br>> CONFIG_HEADERS= /bin/sh ./config.status<br>> config.status: creating po/Makefile.in<br>> config.status: executing depfiles commands<br>> config.status: executing libtool commands<br>> config.status
: executing default-1 commands<br>> config.status: executing bfd_stdint.h commands<br>> config.status: executing default commands<br>> make[3]: Leaving directory<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218/bfd/po'
<br>> make[3]: Entering directory<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218/bfd/po'<br>> make[3]: Nothing to be done for `info'.<br>> make[3]: Leaving directory<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218/bfd/po'
<br>> make[3]: Entering directory<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218/bfd'<br>> make[3]: Nothing to be done for `info-am'.<br>> make[3]: Leaving directory<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218/bfd'
<br>> make[2]: *** [info-recursive] Error 1<br>> make[2]: Leaving directory<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218/bfd'<br>> make[1]: *** [all-bfd] Error 2<br>> make[1]: Leaving directory
<br>> `/home/lvcargnini/puc/instramed/toolchain/build/binutils218'<br>> make: *** [all] Error 2<br>><br>><br>> how to fix this ?<br>> this was I tried the binutils 2.17 instead of 2.18<br>><br>
</div>
</div> Please note that we often get upset with people who top-post:<br>putting a reply underneath the appropriate part of the text helps<br>people follow what is being written.<br><br> Also, you hadn't explained that
2.18 had failed, and you haven't<br>commented on why you were using a different --prefix for what you<br>posted earlier. This means everybody has to guess, and we will<br>often guess wrongly, so please help us to help you. Any other
<br>variations or problems with it that you'd like to mention ? Thanks.<br><br> But, the reason why binutils-2.18 is failing ? Can't tell - all we<br>can see from what you posted above is that a /bin/sh ./config.status
<br>command ran, apparently in bfd/po, and that it was trying to make the<br>info pages. Perhaps it had an error that didn't result in an error<br>message in your log (unlikely). Probably, somewhere before that<br>(perhaps a long way) should be the original error. Trimming the
<br>output is good, perhaps leave a few lines ahead of the original<br>'Error' or 'error' to show any failing command or interesting<br>messages, then snip anything afterwards, it probably isn't going to
<br>bring any useful information (but log the output to a file so that<br>you can go back if somebody needs to ask for more details).<br><br> If you can't find anything, have a look at the config.status script<br>(probably in bfd/po or else in bfd ? ) - look at what it does, if
<br>nothing strikes you as obviously wrong (e.g. trying to run a command<br>from an unset variable) try instrumenting it in an editor, e.g. to<br>echo text telling you where it is, and what it is going to do, with<br>the values of any variables, and the return value in "$?" after
<br>running commands. That is long-winded and tedious, but you need to<br>identify where the problem is. With luck, if you have to do this<br>you'll get lucky and spot something which looks odd.<br><br> Because it is in the info area, I wonder if your host system is
<br>missing the info headers (texinfo-dev or a similarly-named package),<br>or perhaps has a too-old version. But a quick look into the<br>toplevel configure script suggests it will use the 'missing' program<br>
in the toplevel if makeinfo is older than
4.4. That is supposed to<br>touch the output file so that an empty file exists it none was<br>present.<br><br> I think there used to be a bug where something got confused by<br>versions of makeinfo with a double-digit second level (
4.10, 4.11).<br>I never saw that, so I don't know what the symptoms are, but maybe<br>the original error message will point to that sort of thing. If so,<br>I would be tempted to try the binutils branch update patch we are
<br>using in trunk:<br><a href="http://trac.cross-lfs.org/browser/trunk/patches/binutils-2.18-branch_update-3.patch" target="_blank">http://trac.cross-lfs.org/browser/trunk/patches/binutils-2.18-branch_update-3.patch</a>
<br>
<br> If that allows 2.18 to build, I think a better solution (unless<br>the patch arrives in the -sysroot book in the meantime) would be to<br>identify where in the configure script(s) the error happened, then<br>compare that test to the new version and produce a patch for just that
<br>part of the file (the sed which checks the version) and use that in<br>your build. I say that because the branch_update patches are on the<br>bleeding edge, and for a project with few visible users (-sysroot) you<br>
could end up with other problems on a little-used architecture. Of<br>course, if you are happy to debug any resulting problems, testing<br>the branch update is better for the long-term health of the project.<br><br> If you are able to pin this down to a too-new version of makeinfo
<br>on the host, please raise a ticket against binutils in clfs-sysroot<br>(unless that gets updated first).<br><br> And if I was totally wide of the mark and the problem is something<br>else entirely, please disregard the previous 4 paragrahs ;-)
<br><div><div></div><div><br>ĸen<br>--<br>das eine Mal als Tragödie, das andere Mal als Farce<br>_______________________________________________<br>Clfs-dev mailing list<br><a href="mailto:Clfs-dev@lists.cross-lfs.org" target="_blank">
Clfs-dev@lists.cross-lfs.org</a><br><a href="http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org" target="_blank">http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org</a><br></div></div></blockquote>
</div>
<br><br clear="all"><br>-- <br>------------------------------------------------------------------------------<br>Thanks && Regards<br>M.Sc. B.Sc. Luís Vitório Cargnini<br>IEEE Member<br>Electrical Engineer Faculty @ PUCRS
<br>Ipiranga Avenue, 6681 – Building 30 <br>P.O. Box: 90619-900 – Porto Alegre/RS<br>Phone: +55 51 3320 3500 extension: 7696<br>---------------------------------------------------------------------------------