If this is the correct use of ldd...

:~$ ldd /tools/bin/x86_64-lfs-linux-gnu-ranlib
        linux-vdso.so.1 =>  (0x00007fffa837b000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007ff874f03000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff874b3a000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ff87511a000)

Not sure how to tell if that output is correct...

I'm using netrunner 13.06 which is based on ubuntu 12 I think?

host system requirements check scripts gives the following

:~$ ~/code/lfs/version-check.sh
bash, version 4.2.45(1)-release
/bin/sh -> /bin/dash

Binutils: (GNU Binutils for Ubuntu) 2.23.2

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.3-1ubuntu1) 4.7.3

g++ (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3

(Ubuntu EGLIBC 2.17-0ubuntu5.1) 2.17
grep (GNU grep) 2.14
gzip 1.5
Linux version 3.8.0-23-generic (buildd@batsu) (gcc version 4.7.3
(Ubuntu/Linaro 4.7.3-1ubuntu1) ) #34-Ubuntu SMP Wed May 29 20:22:58 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
g++ compilation OK

Which seemed ok, perhaps I missed something there after all?



On Thu, Jan 16, 2014 at 5:23 PM, Ken Moffat <zarniwh...@ntlworld.com> wrote:

> On Thu, Jan 16, 2014 at 04:23:51PM -0600, Louis Rine wrote:
> > Hello all. :)
> >
> > I'v gone through the book a couple times in the past on i686, but this is
> > my first time around with x86_64. All seemed to go well until I ran into
> > this little gem while installing libstdc++:
> >
> > <...lots of compilation output...>
> > Making install in libsupc++
> > make[1]: Entering directory `/mnt/lfs/sources/gcc-build/libsupc++'
> > make[2]: Entering directory `/mnt/lfs/sources/gcc-build/libsupc++'
> > test -z "/tools/lib/../lib64" || /bin/mkdir -p "/tools/lib/../lib64"
> >  /bin/bash ../libtool   --mode=install /usr/bin/install -c   libsupc++.la
> > '/tools/lib/../lib64'
> > libtool: install: /usr/bin/install -c .libs/libsupc++.lai
> > /tools/lib/../lib64/libsupc++.la
> > libtool: install: /usr/bin/install -c .libs/libsupc++.a
> > /tools/lib/../lib64/libsupc++.a
> > libtool: install: chmod 644 /tools/lib/../lib64/libsupc++.a
> > libtool: install: x86_64-lfs-linux-gnu-ranlib
> > /tools/lib/../lib64/libsupc++.a
> > *../libtool: line 1132: x86_64-lfs-linux-gnu-ranlib: command not found*
> > make[2]: *** [install-toolexeclibLTLIBRARIES] Error 127
> > make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/libsupc++'
> > make[1]: *** [install-am] Error 2
> > make[1]: Leaving directory `/mnt/lfs/sources/gcc-build/libsupc++'
> > make: *** [install-recursive] Error 1
> >
> > I checked in /tools/bin, and indeed x86_64-lfs-linux-gnu-ranlib IS there,
> > along with the other stuff that should be there. The lfs user environment
> > seems to be all set up correctly, including $PATH which is
> > /tools/bin:/bin:/usr/bin.
> >
>
>  Perhaps /tools/bin/x86_64-lfs-linux-gnu-ranlib is broken.
> What does 'ldd' say about it ?
>
>  What host system are you using, and did you check all the "host
> system requirements" ?
>
> ĸen
> --
> das eine Mal als Tragödie, dieses Mal als Farce
> --
> 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

Reply via email to