--- Em qui, 13/12/12, JIA Pei escreveu:
De: JIA Pei
Assunto: [lfs-support] error: ‘__EI___isnanf’ aliased to external symbol
‘__GI___isnanf’
Para: lfs-book@l..., lfs-support@...
You cross-posted: lfs-book is for modifications in the book, not
support.
You have sent html. The list members
Richard Melville wrote:
I have one Ethernet adapter (Intel 82574L Gigabit) but udev has found two
complete with MAC addresses. The phantom version is installed on eth0
and
the real version is installed on eth1. I've searched the system for the
phantom MAC address but I cannot find
Richard Melville wrote:
Contents of /etc/udev/rules.d/70-persistent-net.rules:-
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line,
Hi,
I believe the original question was referring to 'libgcc_eh', but you
are referring to 'libgcc_s'.
If you have the same issue as Prabhu (ld cannot find libgcc_eh) then the
instruction is not in the glibc section rather it is in the gcc section
[1] of the book (the very last step).
However
On 12/13/12 04:55, Bruce Dubbs wrote:
William Harrington wrote:
On Dec 12, 2012, at 6:38 PM, Henrik /KaarPoSoft wrote:
I am new to multilib, so I a wondering about stuff like:
- where in the toolchain building sequence should I target multilib? I
tried pass 1, but maybe it would be enough to
On 12/13/12 01:38, Henrik /KaarPoSoft wrote:
Dear all,
I have build LFS and much of BLFS on my ancient 32bit machine.
With a bit of tweaking, I have also got most of it to work on my new
x86_64 machine.
However, I do have a problem:
I need xen virtualization. xen builds a BIOS using the
Hello all,
I am on section 6.4, entering the chroot environment, in LFS Book 7.2 and
when i attempt to chroot I get the following error:
/tools/bin/env: /tools/bin/bash: No such file or directory
This seems to be not too rarely encountered problem but all
the diagnostic checks that I've found
Hello Alex,
Could you send the output of:
$ ls -l /tools/bin/bash
$ /tools/bin/bash --version
Might be a permissions problem.
Also are you running the 'chroot' command as the root user?
Thanks,
Michael
On Fri, 2012-12-14 at 19:22 -0500, Alexander Spitzer wrote:
Hello all,
I am on
Hello Michael,
Thanks for your reply.
Here is the output:
-rwxr-xr-x 1 root root 930472 Dec 13 22:58 /tools/bin/bash
and:
GNU bash, version 4.2.39(1)-release (x86_64-unknown-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
On Fri, Dec 14, 2012 at 07:22:42PM -0500, Alexander Spitzer wrote:
Hello all,
I am on section 6.4, entering the chroot environment, in LFS Book 7.2 and
when i attempt to chroot I get the following error:
/tools/bin/env: /tools/bin/bash: No such file or directory
It's somewhere in the FAQ
Hello Alex,
On Fri, 2012-12-14 at 19:55 -0500, Alexander Spitzer wrote:
Hello Michael,
Thanks for your reply.
Here is the output:
-rwxr-xr-x 1 root root 930472 Dec 13 22:58 /tools/bin/bash
Permissions look good.
and:
GNU bash, version 4.2.39(1)-release (x86_64-unknown-linux-gnu)
Hi Ken,
Running ldd /tools/bin/bash gives:
linux-vdso.so.1 = (0x7fff3d955000)
libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f39676b7000)
libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f39674b3000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f39670f3000)
On Fri, 2012-12-14 at 19:22 -0500, Alexander Spitzer wrote:
Hello all,
I am on section 6.4, entering the chroot environment, in LFS Book 7.2
and when i attempt to chroot I get the following error:
/tools/bin/env: /tools/bin/bash: No such file or directory
No such file or directory doesn't
Hi Simon,
I think that's exactly the problem.
On Fri, Dec 14, 2012 at 8:45 PM, Simon Geard delga...@ihug.co.nz wrote:
No such file or directory doesn't always refer to the actual program
you ran (/tools/bin/bash) - it sometimes means the interpreter for the
program can't be found. If you use
On Fri, Dec 14, 2012 at 08:36:08PM -0500, Alexander Spitzer wrote:
Hi Ken,
Running ldd /tools/bin/bash gives:
linux-vdso.so.1 = (0x7fff3d955000)
libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f39676b7000)
libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2
On Fri, Dec 14, 2012 at 9:45 PM, Ken Moffat zarniwh...@ntlworld.com wrote:
At the moment, I don't recognize your results. Usually, people who
get the correct results from the sanity checks get a good build.
Perhaps there is something different about _how_ you built this.
What host distro
On Fri, 2012-12-14 at 22:26 -0500, Alexander Spitzer wrote:
I did find another clue: when running make for the bash package I
ran into a Permission denied error for yacc and I somehow sudoed my
way around it. Perhaps this resulted in the wrong libraries being
linked because I was not the lfs
On Fri, 2012-12-14 at 21:32 -0500, Alexander Spitzer wrote:
I'm assuming it doesn't work from the inside (i.e. chroot command
gives an error) because it can't get to the interpreter requested:
/lib64/ld-linux-x86-64.so.2
Yes, that'd be correct. That path *will* exist a little later (once you
Simon Geard wrote:
On Fri, 2012-12-14 at 22:26 -0500, Alexander Spitzer wrote:
I did find another clue: when running make for the bash package I
ran into a Permission denied error for yacc and I somehow sudoed my
way around it. Perhaps this resulted in the wrong libraries being
linked
On Fri, Dec 14, 2012 at 11:14 PM, Simon Geard delga...@ihug.co.nz wrote:
Does it work if you simply rebuild bash, according to the instructions
in the book? No need to actually install it - just run the steps up to
make, and run readelf on the resulting binary in order to see if it's
valid.
Alexander Spitzer wrote:
Does the fact that it pointed to dash mean big trouble for all packages
built during chapter 5?
Not necessarily all packages, but glibc for sure.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
21 matches
Mail list logo
