LFS 6.2.5 error in chrooting due to bash needing wide charset ncurses libraries

[Robert Simplicio]

I'm not sure if it's my choice of locale or what have you. I got an error when trying to do the chroot in Chapter 6.4. I am building LFS 6.2.5, from the LFS LiveCD.

/tools/bin/bash: error while loading shared libraries: libcursesw.so.5: cannot[[BR]]
open shared object file: No such file or directory

In researching the issue, I found that in chapter 6.18, the flag --enable-widec is to be used to include wide charset libraries. I suggest updating chapter 5.13 to include this. If this is approved, I will be happy to make and commit the change to the book myself.

[Robert Simplicio]

Corrected keyword for libcursesw.

[ken@…]

Maybe it is your choice of locale (you haven't specified what you are using). but in section 4.4 we put the following into /home/lfs/.bashrc -

LC_ALL=POSIX
PATH=/tools/bin:/bin:/usr/bin
export LFS LC_ALL PATH

so you ought to be in 'POSIX'. I suggest that either you you missed that, or else you inadvertently used 'su -' to become root, instead of 'su'.

Alternatively, /tools/bin/bash is somehow linked against some of the host's libraries.

For what it's worth, commit rights to the book are not the same as commit rights to this wiki. But anybody can send patches to the book's xml sources (to the lfs-dev list) for identified errors.

I'll keep this open for the moment, in case you think I've missed something important (wouldn't be the first time), but at the moment I think this is invalid.

[alexander@…]

This is not a bug in the book. /tools/bin/bash cannot be linked against libncursesw at any stage. It is always linked against /tools/lib/libncurses.so.5.

Ken: locale is irrelevant here.

[ken@…]

Agreed - I was trying to encourage the OP to give full details when he asks for help.

[Jeremy Huntwork]

Milestone 6.3 deleted