On Sun, 2012-12-02 at 15:01 +1300, Simon Geard wrote:
I think Ken has pointed me in the right direction - bash links not to
libncurses or libncursesw, but to plain-old libcurses, and I seem to
have missed the commands that create the linker script that redirects
that one. I've just fixed it,
On Sun, 2012-12-02 at 21:14 +1300, Simon Geard wrote:
And just to confirm, that was it. Not a problem with the linker like I'd
assumed - just a missed step in the ncurses build. Seeing as it was
complaining about libncurses (rather than libcurses) not being found, it
never occurred to me to
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of course, this should say that it's looking for the dynamic
linker in /lib. Then verify you actually have all the right libraries
for Ncurses: ls -la
On Dec 1, 2012, at 4:59 AM, Simon Geard wrote:
Basically, I'm hoping that someone more familiar than me with the
toolchain can tell me how a chapter 6 package (bash) might be linked
against a library not installed in chapter 6 (the non-wide version of
ncurses). The obvious answer is that it's
On Nov 30, 2012, at 5:37 AM, Simon Geard wrote:
/bin/bash: error while loading shared libraries: libncurses.so.5:
cannot
open shared object file: No such file or directory
Do you also get the same problem when running /bin/more /sbin/cfdisk
and /usr/bin/cal ?
Those are installed by
On Sat, Dec 01, 2012 at 11:59:07PM +1300, Simon Geard wrote:
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of course, this should say that it's looking for the dynamic
linker in /lib. Then verify you actually
On Sat, 01 Dec 2012 23:59:07 +1300
Simon Geard delga...@ihug.co.nz wrote:
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of course, this should say that it's looking for the
dynamic linker in /lib. Then verify
On Sat, 1 Dec 2012 16:19:38 +0100
Aleksandar Kuktin akuk...@gmail.com wrote:
On Sat, 01 Dec 2012 23:59:07 +1300
Simon Geard delga...@ihug.co.nz wrote:
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of
On Sat, 1 Dec 2012 16:24:08 +0100
Aleksandar Kuktin akuk...@gmail.com wrote:
I mean `ldd /path/to/bash/that/is/the/problem/bash'.
Also, there is an easy way to test if the problem is linking with a
library from /tools. Make a symlink.
ln -sv /usr /tools
Then try it again.
Or maybe
On Sat, 2012-12-01 at 16:19 +0100, Aleksandar Kuktin wrote:
Can you do `ldd /bin/bash'?
Oddly, no. I can't use ldd because that's a shell script depending
on /bin/sh working, but if I run:
/lib/ld-linux-x86-64.so.2 --list /bin/bash
...I get:
/bin/bash: error while loading shared libraries:
On Sat, 2012-12-01 at 07:27 -0600, William Harrington wrote:
On Nov 30, 2012, at 5:37 AM, Simon Geard wrote:
/bin/bash: error while loading shared libraries: libncurses.so.5:
cannot
open shared object file: No such file or directory
Do you also get the same problem when running
Hey guys...
Rewriting my LFS build scripts, I'm getting an interesting linking error
with bash in chapter 6, and am hoping someone can point me in the right
direction for tracking down the cause.
Basically, bash builds correctly, but the resulting binary is bad, any
attempt to invoke it
12 matches
Mail list logo
