LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)
-   -   GCC Second pass fails (https://www.linuxquestions.org/questions/linux-from-scratch-13/gcc-second-pass-fails-350490/)

thelonewolf 08-06-2005 01:56 AM
[SOLVED] GCC Second pass fails
 
Ok, I keep looking for an answer to this with no luck. Any idea what the heck is going on with this? This is from the second pass of GCC



Code:
Configuring in x86_64-unknown-linux-gnu/libstdc++-v3
configure: loading cache ./config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for x86_64-unknown-linux-gnu-gcc...  /mnt/lfs/sources/gcc-build/gcc/xgcc -B/mnt/lfs/sources/gcc-build/gcc/ -B/tools/x86_64-unknown-linux-gnu/bin/ -B/tools/x86_64-unknown-linux-gnu/lib/ -isystem /tools/x86_64-unknown-linux-gnu/include -isystem /tools/x86_64-unknown-linux-gnu/sys-include
checking for C compiler default output... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make: *** [configure-target-libstdc++-v3] Error 1
Here's config.log:


Code:
configure:581: checking host system type
configure:602: checking target system type
configure:620: checking build system type
configure:675: checking for a BSD compatible install
configure:2859: checking for x86_64-unknown-linux-gnu-ar
configure:2892: checking for ar
configure:2931: checking for x86_64-unknown-linux-gnu-as
configure:2964: checking for as
configure:3003: checking for x86_64-unknown-linux-gnu-dlltool
configure:3036: checking for dlltool
configure:3075: checking for x86_64-unknown-linux-gnu-ld
configure:3147: checking for x86_64-unknown-linux-gnu-nm
configure:3180: checking for nm
configure:3219: checking for x86_64-unknown-linux-gnu-ranlib
configure:3252: checking for ranlib
configure:3291: checking for x86_64-unknown-linux-gnu-windres
configure:3324: checking for windres
configure:3363: checking for x86_64-unknown-linux-gnu-objcopy
configure:3396: checking for objcopy
configure:3435: checking for x86_64-unknown-linux-gnu-objdump
configure:3468: checking for objdump
configure:3517: checking for x86_64-unknown-linux-gnu-ar
configure:3550: checking for ar
configure:3589: checking for x86_64-unknown-linux-gnu-as
configure:3622: checking for as
configure:3661: checking for x86_64-unknown-linux-gnu-dlltool
configure:3694: checking for dlltool
configure:3733: checking for x86_64-unknown-linux-gnu-ld
configure:3766: checking for ld
configure:3805: checking for x86_64-unknown-linux-gnu-nm
configure:3838: checking for nm
configure:3877: checking for x86_64-unknown-linux-gnu-ranlib
configure:3910: checking for ranlib
configure:3949: checking for x86_64-unknown-linux-gnu-windres
configure:3982: checking for windres
configure:4049: checking whether to enable maintainer-specific portions of Makefiles

mlinuxk 08-06-2005 11:07 AM
I had a similar problem when I did the second pass also, I was running the new build in the old directory. After I started over again, I notice that I needed to build a new directory for every build and I had no more problems, until I got to psmisc. Just a thought.


All times are GMT -5. The time now is 10:13 PM.