On 06/17/2016 09:29 PM, Ken Moffat wrote:
On Fri, Jun 17, 2016 at 05:25:49PM -0500, [email protected] wrote:
On 06/17/2016 04:12 PM, Paul Rogers wrote:
ldd /bin/bash shows:
linux-vdso.so.1 (0x00007ffe871bf000)
libreadline.so.6 => /lib/libreadline.so.6 (0x00007fa9061a8000)
libhistory.so.6 => /lib/libhistory.so.6 (0x00007fa905fa0000)
libncursesw.so.6 => /lib/libncursesw.so.6 (0x00007fa905d36000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fa905b32000)
libc.so.6 => /lib/libc.so.6 (0x00007fa905791000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa9063ed000)
Do you get any similar error when just running "/bin/bash"?
Yes, I receive the same error.
So do all of those libraries exist? IANM, you'll get the same message
if one of the libraries it needs isn't found.
All exist but for linux-vdso.so.1. However, I responded to the /bin/bash
question wrong. I do NOT receive the error with "/bin/bash." My mistake.
With current binutils, if libfoo.so.7 is not present then ldd says
something like
'not found'
after the soname, instead of
=> /usr/lib/libfoo.so.7 (hexdigits)
But I'm still none the wiser about what is wrong, and casting around
for whatever we are all overlooking. If you can invoke
a new shell with /bin/bash without the message, do you get the
message when you try to invoke /bin/sh ?
And can you do things like /bin/bash SomeScript.sh without the
message ? Ditto for /bin/sh ?
ĸen
/bin/sh does not produce the error, but does change my prompt, which
/bin/bash does not.
/bin/bash SomeScript.sh and /bin/sh SomeScript.sh both produce the error.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
