Re: [lfs-support] Problems in Binutils Pass 2
Thanks for the reply. I definitely set them last night, and I just tried again this morning, checking them before configuring: lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ AR=$LFS_TGT-ar lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ RANLIB=$LFS_TGT-ranlib lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ echo $CC $AR $RANLIB x86_64-lfs-linux-gnu-gcc x86_64-lfs-linux-gnu-ar x86_64-lfs-linux-gnu-ranlib ..same error on configure. The LFS_TGT is set directly from the .bashrc, which I copy/pasted straight out of the book. Something interesting: lfs@voxbox-dev:/mnt/lfs/tools$ ls bin include lib64 sbin var x86_64-unknown-linux-gnu etc lib libexec share x86_64-lfs-linux-gnu That unknown-linux stuff might however be left over from when I tried to make (and I guess make install) binutils after missing that error the first time. I've got to stop trying this stuff so late in the evening. But anyway, tools/bin seems to have the necessary stuff: lfs@voxbox-dev:/mnt/lfs/tools/bin$ ls x86_64-lfs-linux-gnu-gcc* x86_64-lfs-linux-gnu-gcc x86_64-lfs-linux-gnu-gcc-ar x86_64-lfs-linux-gnu-gcc-ranlib x86_64-lfs-linux-gnu-gcc-4.7.2 x86_64-lfs-linux-gnu-gcc-nm lfs@voxbox-dev:/mnt/lfs/tools/bin$ echo $PATH /tools/bin:/bin:/usr/bin Maybe I screwed up one of the previous stages, and something bad got hard coded? I'm trying this all without a clear head, so maybe I should start over when I feel more up to it. On Thu, 4 Apr, 2013 at 10:29 PM, Pierre Labastie pierre.labas...@neuf.fr wrote: Le 04/04/2013 23:05, Alex Stefan Kaye a écrit : Hi all, I've just started my LFS journey, and I've hit upon a problem when running configure during binutils pass 2. I've not deviated from the book at all (discounting any mistakes I've not noticed - it's late here, but I've been careful). The error: checking for C compiler default output file name... configure: error: in `/mnt/lfs/sources/binutils-build': configure: error: C compiler cannot create executables From your config.log: configure:3767: checking for gcc configure:3783: found /usr/bin/gcc configure should find x86_64-lfs-linux-gnu-gcc! Have you typed the three lines: CC=$LFS_TGT-gcc\ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ before configure? Or Maybe $LFS_TGT is not set correctly. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems in Binutils Pass 2
Le 05/04/2013 12:22, Alex Stefan Kaye a écrit : Thanks for the reply. I definitely set them last night, and I just tried again this morning, checking them before configuring: lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ AR=$LFS_TGT-ar lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ RANLIB=$LFS_TGT-ranlib lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ echo $CC $AR $RANLIB x86_64-lfs-linux-gnu-gcc x86_64-lfs-linux-gnu-ar x86_64-lfs-linux-gnu-ranlib When you enter: Variable-name=something `Variable_name' is defined locally in the shell you are running. It is not _exported_ (to any command you launch). So, when you do like that, `configure' ignores the values you have set for CC, AR and RANLIB. You can do: export CC=... But then, CC is exported for any command in that shell, which is not what you want after building gcc. To export variables to only one command, you type: Variable_name=something command Then the value of Variable_name is set for the execution of command. That is the approach in the book: CC=$LFS_TGT-gcc \ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ ../binutils-2.23.2/configure \ --prefix=/tools \ --disable-nls \ --with-lib-path=/tools/lib \ --with-sysroot Notice the \ at the end of each line (the \ must be immediately followed by return, no space), which means it is equivalent to: CC=$LFS_TGT-gcc AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib ../binutils-2.23.2/configure --prefix=/tools... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Problems in Binutils Pass 2
D'oh! just doesn't quite cut it. I saw something like that in Google, but misunderstood the meaning. That makes perfect sense. Thanks very much Pierre. On Fri, 5 Apr, 2013 at 11:46 AM, Pierre Labastie pierre.labas...@neuf.fr wrote: Le 05/04/2013 12:22, Alex Stefan Kaye a écrit : Thanks for the reply. I definitely set them last night, and I just tried again this morning, checking them before configuring: lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ AR=$LFS_TGT-ar lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ RANLIB=$LFS_TGT-ranlib lfs@voxbox-dev:/mnt/lfs/sources/binutils-build$ echo $CC $AR $RANLIB x86_64-lfs-linux-gnu-gcc x86_64-lfs-linux-gnu-ar x86_64-lfs-linux-gnu-ranlib When you enter: Variable-name=something `Variable_name' is defined locally in the shell you are running. It is not _exported_ (to any command you launch). So, when you do like that, `configure' ignores the values you have set for CC, AR and RANLIB. You can do: export CC=... But then, CC is exported for any command in that shell, which is not what you want after building gcc. To export variables to only one command, you type: Variable_name=something command Then the value of Variable_name is set for the execution of command. That is the approach in the book: CC=$LFS_TGT-gcc \ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ ../binutils-2.23.2/configure \ --prefix=/tools \ --disable-nls \ --with-lib-path=/tools/lib \ --with-sysroot Notice the \ at the end of each line (the \ must be immediately followed by return, no space), which means it is equivalent to: CC=$LFS_TGT-gcc AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib ../binutils-2.23.2/configure --prefix=/tools... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Problems in Binutils Pass 2
Hi all, I've just started my LFS journey, and I've hit upon a problem when running configure during binutils pass 2. I've not deviated from the book at all (discounting any mistakes I've not noticed - it's late here, but I've been careful). The error: checking for C compiler default output file name... configure: error: in `/mnt/lfs/sources/binutils-build': configure: error: C compiler cannot create executables I've attached my config.log, and there's further information below. Thanks in advance. LFS Book Version: 7.3 Host Info: Ubuntu 13.04 (daily build) x86_64 3.8.0-15-generic Version Check Output: bash, version 4.2.37(1)-release /bin/sh - /bin/bash Binutils: (GNU Binutils for Ubuntu) 2.23.1 bison (GNU Bison) 2.5 /usr/bin/yacc - /usr/bin/bison.yacc bzip2, Version 1.0.6, 6-Sept-2010. Coreutils: 8.20 diff (GNU diffutils) 3.2 find (GNU findutils) 4.4.2 GNU Awk 4.0.1 /usr/bin/awk - /usr/bin/gawk gcc (Ubuntu/Linaro 4.7.2-22ubuntu5) 4.7.2 (Ubuntu EGLIBC 2.17-0ubuntu4) 2.17 grep (GNU grep) 2.14 gzip 1.5 Linux version 3.8.0-15-generic (buildd@lamiak) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-22ubuntu4) ) #25-Ubuntu SMP Wed Mar 27 19:19:30 UTC 2013 m4 (GNU M4) 1.4.16 GNU Make 3.81 patch 2.6.1 Perl version='5.14.2'; GNU sed version 4.2.1 tar (GNU tar) 1.26 Texinfo: makeinfo (GNU texinfo) 4.13 xz (XZ Utils) 5.1.0alpha gcc compilation OK This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.64. Invocation command line was $ ../binutils-2.23.1/configure --prefix=/tools --disable-nls --with-lib-path=/tools/lib ## - ## ## Platform. ## ## - ## hostname = voxbox-dev uname -m = x86_64 uname -r = 3.8.0-15-generic uname -s = Linux uname -v = #25-Ubuntu SMP Wed Mar 27 19:19:30 UTC 2013 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /tools/bin PATH: /bin PATH: /usr/bin ## --- ## ## Core tests. ## ## --- ## configure:2237: checking build system type configure:2251: result: x86_64-unknown-linux-gnu configure:2298: checking host system type configure:2311: result: x86_64-unknown-linux-gnu configure:2331: checking target system type configure:2344: result: x86_64-unknown-linux-gnu configure:2398: checking for a BSD-compatible install configure:2466: result: /usr/bin/install -c configure:2477: checking whether ln works configure:2499: result: yes configure:2503: checking whether ln -s works configure:2507: result: yes configure:2514: checking for a sed that does not truncate output configure:2578: result: /bin/sed configure:2587: checking for gawk configure:2603: found /usr/bin/gawk configure:2614: result: gawk configure:3767: checking for gcc configure:3783: found /usr/bin/gcc configure:3794: result: gcc configure:4023: checking for C compiler version configure:4032: gcc --version 5 gcc (Ubuntu/Linaro 4.7.2-22ubuntu5) 4.7.2 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:4043: $? = 0 configure:4032: gcc -v 5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.7.2-22ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --with-system-zlib --enable-objc-gc --with-cloog --enable-cloog-backend=ppl --disable-cloog-version-check --disable-ppl-version-check --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-22ubuntu5) configure:4043: $? = 0 configure:4032: gcc -V 5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:4043: $? = 4 configure:4032: gcc -qversion 5 gcc: error: unrecognized command line option '-qversion' gcc: fatal error: no input files compilation terminated. configure:4043: $? = 4 configure:4063: checking for C compiler default output file name configure:4085: gcc
Re: [lfs-support] Problems in Binutils Pass 2
Le 04/04/2013 23:05, Alex Stefan Kaye a écrit : Hi all, I've just started my LFS journey, and I've hit upon a problem when running configure during binutils pass 2. I've not deviated from the book at all (discounting any mistakes I've not noticed - it's late here, but I've been careful). The error: checking for C compiler default output file name... configure: error: in `/mnt/lfs/sources/binutils-build': configure: error: C compiler cannot create executables From your config.log: configure:3767: checking for gcc configure:3783: found /usr/bin/gcc configure should find x86_64-lfs-linux-gnu-gcc! Have you typed the three lines: CC=$LFS_TGT-gcc\ AR=$LFS_TGT-ar \ RANLIB=$LFS_TGT-ranlib \ before configure? Or Maybe $LFS_TGT is not set correctly. Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
