Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My guess would be that your static version of bash was not configured properly or did not compile properly. Try recompiling the static version of bash and pay very close attention to the options and any prerequisites (i.e. the curses and ncurses libraries mentioned immediately before you compile bash).
As a personal preference, when I recompile software that gives me trouble, I delete its source tree (i.e. "rm -rf bash-2.05b"). Then I replace it by untar-ing the source from the packages again. It's not really necessary, but gives me a nice, warm, and fuzzy feeling.
Originally posted by Dark_Helmet My guess would be that your static version of bash was not configured properly or did not compile properly. Try recompiling the static version of bash and pay very close attention to the options and any prerequisites (i.e. the curses and ncurses libraries mentioned immediately before you compile bash).
IT didnt want to compile because it didnt find curses so I reconfigured and omitted --with-curses. It worked.
I dont believe that could cause problems.
Should I upgrade ncurses on My Slackware 8.1???
Quote:
As a personal preference, when I recompile software that gives me trouble, I delete its source tree (i.e. "rm -rf bash-2.05b"). Then I replace it by untar-ing the source from the packages again. It's not really necessary, but gives me a nice, warm, and fuzzy feeling.
1) I've never tried compiling bash without the ncurses library
2) I've never had problems compiling bash with the exception of having to specify the system type for the configure scipt
In other words, any information following this should be prefaced with "I'm no expert, but this might work..."
To be honest, I don't exactly know what the ncurses library is used for. Removing it may leave bash lacking some functionality that LFS requires later down the road. That being my paranoid stance, I'd try to upgrade ncurses. I don't know what version LFS wants or what slackware comes bundled with, but since revision 4.0 of the LFS book was released within a month or two, I think it's safe to assume they were using a relatively recent version of the library.
Hmm, I guess Bash really needed curses.. compiled ncurses 5.3 ( on Slack 8.1 default is 5.2 ) and recompiled Bash with curses flag and now I can chroot normally
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.