--- On Sat, 2/27/10, Bruce Dubbs <[email protected]> wrote:

> From: Bruce Dubbs <[email protected]>
> Subject: Re: Correction confirmed to CH5 GCC pass 1 or pre-requisites needs 
> changing.
> To: "LFS Book Maintenance List" <[email protected]>
> Date: Saturday, February 27, 2010, 10:13 PM
> Test Man wrote:
> 
> > bash, version 2.05b.0(1)-release
> > /bin/sh -> /bin/bash
> > Binutils: version 2.14 20030612
> > bison (GNU Bison) 1.875
> > /usr/bin/yacc -> /usr/bin/yacc
> > bzip2,  Version 1.0.2, 30-Dec-2001.
> > Coreutils:  5.0
> > diff (GNU diffutils) 2.8.1
> > GNU find version 4.1.20
> > GNU Awk 3.1.3
> > /usr/bin/awk -> /usr/bin/gawk
> > gcc (GCC) 3.3.1
> > GNU C Library stable release version 2.3.2,
> > grep (GNU grep) 2.5.1
> > gzip 1.3.5
> > Linux version
> >  2.6.32.8-i386-monolithic (r...@p166) (gcc
> version 3.3.1) #2 Mon Feb 22 10:48:38 GMT 2010
> > GNU m4 1.4
> > GNU Make 3.80
> > patch 2.5.4
> > Perl version='5.8.0';
> > GNU sed version 4.0.7
> > tar (GNU tar) 1.13.25
> > Texinfo: makeinfo (GNU texinfo) 4.6
> > Compilation OK
> >
> --------------------------------------------------------------------
> > 
> > But, Ch 5 gcc-4.4.3 Pass 1 fails with:
> > 
> > "checking for library containing strerror...
> configure: error: Link
> > tests are not allowed after GCC_NO_EXECUTABLES".
> 
> That's interesting.  I've never seen that before, but
> on my system 
> (64-bit), I have:
> 
> checking for library containing strerror... none required
> 
> libiberty/configure has that section:
> 
> if test x$gcc_no_link = xyes; then
>    { { echo "$as_me:$LINENO: error: Link
> tests are not allowed after 
> GCC_NO_EXECUTABLES."
> 
> Following back:
> 
> if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
>    (eval $ac_link) 2>&5
>    ac_status=$?
>    echo "$as_me:$LINENO: \$? = $ac_status"
> >&5
>    (exit $ac_status); }; then
>    gcc_no_link=no
> else
>    gcc_no_link=yes
> fi
> 
> What we are doing is effectively cross compiling and it
> looks like there 
> is a problem earlier in building binutils.
> 
>    -- Bruce
> -- 
> http://linuxfromscratch.org/mailman/listinfo/lfs-book
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
> 


Hello Bruce,

I've tested this on the following CPU architectures:

Intel i486-SX/20
Intel i486-DX/100
AMD K6-2/500
Xeon L5420/2500 Dual SMP

In all the above cases, the exact same behaviour is exhibited as that shown by 
the Classic Pentium 166 build.

Below is the output leading up to the error (taken from the AMD K6-2/500 build 
session):

======================================================
Checking multilib configuration for libiberty...
mkdir -p -- i586-MyLFS-linux-gnu/libiberty
Configuring in i586-MyLFS-linux-gnu/libiberty
configure: creating cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles... no
checking for makeinfo... makeinfo --split-size=5000000
checking for perl... perl
checking build system type... i586-pc-linux-gnu
checking host system type... i586-MyLFS-linux-gnu
checking for i586-MyLFS-linux-gnu-ar... /tools/i586-MyLFS-linux-gnu/bin/ar
checking for i586-MyLFS-linux-gnu-ranlib... 
/tools/i586-MyLFS-linux-gnu/bin/ranlib
checking for i586-MyLFS-linux-gnu-gcc... 
/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include accepts -g... yes
checking for /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include option to accept ANSI C... 
none needed
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for _LARGE_FILES value needed for large files... no
checking how to run the C preprocessor... 
/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include -E
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include supports -W... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include supports -Wall... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include supports -Wwrite-strings... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include supports -Wc++-compat... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include supports 
-Wstrict-prototypes... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include supports -pedantic ... yes
checking whether /mnt/lfs/sources/newLFS/q/gcc-build/./gcc/xgcc 
-B/mnt/lfs/sources/newLFS/q/gcc-build/./gcc/ -B/tools/i586-MyLFS-linux-gnu/bin/ 
-B/tools/i586-MyLFS-linux-gnu/lib/ -isystem /tools/i586-MyLFS-linux-gnu/include 
-isystem /tools/i586-MyLFS-linux-gnu/sys-include and cc understand -c and -o 
together... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether byte ordering is bigendian... no
checking for a BSD-compatible install... /bin/install -c
checking for sys/file.h... no
checking for sys/param.h... no
checking for limits.h... yes
checking for stdlib.h... no
checking for malloc.h... no
checking for string.h... no
checking for unistd.h... no
checking for strings.h... no
checking for sys/time.h... no
checking for time.h... no
checking for sys/resource.h... no
checking for sys/stat.h... no
checking for sys/mman.h... no
checking for fcntl.h... no
checking for alloca.h... no
checking for sys/pstat.h... no
checking for sys/sysmp.h... no
checking for sys/sysinfo.h... no
checking for machine/hal_sysinfo.h... no
checking for sys/table.h... no
checking for sys/sysctl.h... no
checking for sys/systemcfg.h... no
checking for stdint.h... no
checking for stdio_ext.h... no
checking for sys/wait.h that is POSIX.1 compatible... no
checking whether time.h and sys/time.h may both be included... no
checking whether errno must be declared... yes
checking for egrep... grep -E
checking for ANSI C header files... no
checking for sys/types.h... no
checking for sys/stat.h... (cached) no
checking for stdlib.h... (cached) no
checking for string.h... (cached) no
checking for memory.h... no
checking for strings.h... (cached) no
checking for inttypes.h... no
checking for stdint.h... (cached) no
checking for unistd.h... (cached) no
checking for int... no
checking size of int... 0
checking for uintptr_t... no
checking for a 64-bit type... unsigned long long
checking for pid_t... no
checking for library containing strerror... configure: error: Link tests are 
not allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libiberty] Error 1
make[1]: Leaving directory `/mnt/lfs/sources/newLFS/q/gcc-build'
make: *** [all] Error 2
======================================================

The failure appears to occur at the start of the second build of GCC (i.e. 
while building Stage 1) - do you agree?

Can I ask how you performed your test - i.e. was it built from a i386 LFS 5.0 
image?

If not, would you be able to test this or could someone else who has access to 
an i386 LFS 5.0 image to confirm my observations?

regards,

Mr Nobby.


      

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to