Hello All,

It's unclear whether the email list is restricted to just the stable version-- 
if so, just say the word and I'll abandon DEV for STABLE.  If not, I could use 
a hand figuring out the cause of an install failure.

The details:
1) Building to a blank system, using Debian Live CD 
(debian-live-6.0.3-i386-rescue), which includes all necessary build tools.

2) As stated, I'm following LFS-DEV (SVN-20111201) to the letter with a couple 
minor deviations.

3) Deviations to the book are limited to:
    Adding lfs user to sudoers file with 'ALL=(ALL)  NOPASSWD: ALL'.

    Using indirect $SPECS file creation in _5.8. Adjusting the Toolchain_ by 
doing
                $LFS_TGT-gcc -dumpspecs | sed \
                -e 's@/lib\(64\)\?/ld@/tools&@g' \
                -e "/^\*cpp:$/{n;s,$, -isystem /tools/include,}" > ./specs
                sudo mv ./specs 
/mnt/lfs/tools/bin/../lib/gcc/i686-lfs-linux-gnu/4.6.2
    instead of the direct method
                $LFS_TGT-gcc -dumpspecs | sed \
                  -e 's@/lib\(64\)\?/ld@/tools&@g' \
                  -e "/^\*cpp:$/{n;s,$, -isystem /tools/include,}" > $SPECS
    used in the book.

4) So far all steps have executed without a hitch, until reaching the install 
step of _5.9.1. Installation of Binutils_.  Then the following is reported:
  lfs@debian:/mnt/lfs/sources/binutils-build$ cat install.log
  make[1]: Entering directory `/mnt/lfs/sources/binutils-build'
  /bin/bash ../binutils-2.22/mkinstalldirs /tools /tools
  make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
  make  install-recursive
  make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
  Making install in doc
  make[4]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
  test -z "/tools/share/info" || /bin/mkdir -p "/tools/share/info"
   /usr/bin/install -c -m 644 ../../../binutils-2.22/bfd/doc/bfd.info 
'/tools/share/info'
   install-info --info-dir='/tools/share/info' '/tools/share/info/bfd.info'
  This is not dpkg install-info anymore, but GNU install-info
  See the man page for ginstall-info for command line arguments
  make[4]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
  Making install in po
  make[4]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/po'
  make[4]: Nothing to be done for `install'.
  make[4]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/po'
  make[4]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
  make[5]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
  make[5]: Nothing to be done for `install-exec-am'.
  test -z "/tools/include" || /bin/mkdir -p "/tools/include"
   /usr/bin/install -c -m 644 bfd.h 
../../binutils-2.22/bfd/../include/ansidecl.h 
../../binutils-2.22/bfd/../include/symcat.h 
../../binutils-2.22/bfd/../include/bfdlink.h '/tools/include'
  test -z "/tools/lib" || /bin/mkdir -p "/tools/lib"
   /bin/bash ./libtool   --mode=install /usr/bin/install -c   libbfd.la 
'/tools/lib'
  libtool: install: /usr/bin/install -c .libs/libbfd.lai /tools/lib/libbfd.la
  libtool: install: /usr/bin/install -c .libs/libbfd.a /tools/lib/libbfd.a
  libtool: install: chmod 644 /tools/lib/libbfd.a
  libtool: install: i686-lfs-linux-gnu-ranlib /tools/lib/libbfd.a
  ./libtool: line 1118: i686-lfs-linux-gnu-ranlib: command not found
  make[5]: *** [install-bfdlibLTLIBRARIES] Error 127
  make[5]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
  make[4]: *** [install-am] Error 2
  make[4]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
  make[3]: *** [install-recursive] Error 1
  make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
  make[2]: *** [install] Error 2
  make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
  make[1]: *** [install-bfd] Error 2
  make[1]: Leaving directory `/mnt/lfs/sources/binutils-build'
  make: *** [install] Error 
The relevant lines are:
  libtool: install: i686-lfs-linux-gnu-ranlib /tools/lib/libbfd.a
  ./libtool: line 1118: i686-lfs-linux-gnu-ranlib: command not found

However, 'i686-lfs-linux-gnu-ranlib' exists and is executable:
  lfs@debian:/mnt/lfs/sources/binutils-build$ which i686-lfs-linux-gnu-ranlib
  /tools/bin/i686-lfs-linux-gnu-ranlib

  lfs@debian:/mnt/lfs/sources/binutils-build$ i686-lfs-linux-gnu-ranlib
  Usage: i686-lfs-linux-gnu-ranlib [options] archive
   Generate an index to speed access to archives
   The options are:
    @<file>                      Read options from <file>
    -t                           Update the archive's symbol map timestamp
    -h --help                    Print this help message
    -v --version                 Print version information
  i686-lfs-linux-gnu-ranlib: supported targets: elf32-i386 a.out-i386-linux 
pei-i386 elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
Checking /mnt/lfs/sources/binutils-build/bdf/libtool: line 1118 isn't too 
helpful as it is:
  ...
  # func_show_eval cmd [fail_exp]
  # Unless opt_silent is true, then output CMD.  Then, if opt_dryrun is
  # not true, evaluate CMD.  If the evaluation of CMD fails, and FAIL_EXP
  # is given, then evaluate it.
  func_show_eval ()
  {
      my_cmd="$1"
      my_fail_exp="${2-:}"

      ${opt_silent-false} || {
        func_quote_for_expand "$my_cmd"
        eval "func_echo $func_quote_for_expand_result"
      }

      if ${opt_dry_run-false}; then :; else
        eval "$my_cmd"       <===========================( This is line 1118 )
        my_status=$?
        if test "$my_status" -eq 0; then :; else
          eval "(exit $my_status); $my_fail_exp"
        fi
      fi
  }
  ...
which isn't apparent to me...

/mnt/lfs/tools lists:
  -rwxr-xr-x 1 root root    3397 Dec  4 21:00 catchsegv*
  -rwxr-xr-x 1 root root   65419 Dec  4 20:59 gencat*
  -rwxr-xr-x 1 root root   41023 Dec  4 20:59 getconf*
  -rwxr-xr-x 1 root root   61553 Dec  4 21:00 getent*
  -rwxr-xr-x 1 root root 2899544 Dec  4 15:53 i686-lfs-linux-gnu-addr2line*
  -rwxr-xr-x 2 root root 3022263 Dec  4 15:53 i686-lfs-linux-gnu-ar*
  -rwxr-xr-x 2 root root 4299504 Dec  4 15:53 i686-lfs-linux-gnu-as*
  -rwxr-xr-x 1 root root 2860805 Dec  4 15:53 i686-lfs-linux-gnu-c++filt*
  -rwxr-xr-x 1 root root  686890 Dec  4 20:21 i686-lfs-linux-gnu-cpp*
  -rwxr-xr-x 1 root root   60396 Dec  4 15:53 i686-lfs-linux-gnu-elfedit*
  -rwxr-xr-x 2 root root  674867 Dec  4 20:21 i686-lfs-linux-gnu-gcc*
  -rwxr-xr-x 2 root root  674867 Dec  4 20:21 i686-lfs-linux-gnu-gcc-4.6.2*
  -rwxr-xr-x 1 root root   86749 Dec  4 20:21 i686-lfs-linux-gnu-gcov*
  -rwxr-xr-x 1 root root 3300225 Dec  4 15:53 i686-lfs-linux-gnu-gprof*
  -rwxr-xr-x 4 root root 4089777 Dec  4 15:53 i686-lfs-linux-gnu-ld*
  -rwxr-xr-x 4 root root 4089777 Dec  4 15:53 i686-lfs-linux-gnu-ld.bfd*
  -rwxr-xr-x 2 root root 2920079 Dec  4 15:53 i686-lfs-linux-gnu-nm*
  -rwxr-xr-x 2 root root 3443090 Dec  4 15:53 i686-lfs-linux-gnu-objcopy*
  -rwxr-xr-x 2 root root 4036461 Dec  4 15:53 i686-lfs-linux-gnu-objdump*
  -rwxr-xr-x 2 root root 3022258 Dec  4 15:53 i686-lfs-linux-gnu-ranlib*
  -rwxr-xr-x 1 root root  627697 Dec  4 15:53 i686-lfs-linux-gnu-readelf*
  -rwxr-xr-x 1 root root 2914676 Dec  4 15:53 i686-lfs-linux-gnu-size*
  -rwxr-xr-x 1 root root 2888697 Dec  4 15:53 i686-lfs-linux-gnu-strings*
  -rwxr-xr-x 2 root root 3443089 Dec  4 15:53 i686-lfs-linux-gnu-strip*
  -rwxr-xr-x 1 root root  199282 Dec  4 20:59 iconv*
  -rwxr-xr-x 1 root root    5788 Dec  4 21:00 ldd*
  -rwxr-xr-x 1 root root   16567 Dec  4 21:00 lddlibc4*
  -rwxr-xr-x 1 root root   99174 Dec  4 20:59 locale*
  -rwxr-xr-x 1 root root  976129 Dec  4 20:59 localedef*
  -rwxr-xr-x 1 root root    6485 Dec  4 20:59 mtrace*
  -rwxr-xr-x 1 root root   23718 Dec  4 21:00 pcprofiledump*
  -rwxr-xr-x 1 root root  217377 Dec  4 21:00 rpcgen*
  -rwxr-xr-x 1 root root    4265 Dec  4 21:00 sotruss*
  -rwxr-xr-x 1 root root   62867 Dec  4 21:00 sprof*
  -rwxr-xr-x 1 root root    7133 Dec  4 20:59 tzselect*
  -rwxr-xr-x 1 root root    5374 Dec  4 21:00 xtrace*

I'd appreciate help with this one.  I mean it's weird, amiright?  Btw config, 
build, and install logs are available from all steps after the binutils-1st 
pass step, which were mistakenly deleted with the source from that step...

Thanks for the time.

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

Reply via email to