On 4/15/07, Gabriel Barazer <[EMAIL PROTECTED]> wrote:
>
> I am wondering how readline 5.2 must be compiled with an explicit link
> to libncurses in the CLFS book ? There is a major disadvantage doing
> this : when compiling bash, it links against readline (by the option
> --with-installed-readline, which MUST be used to avoid the bugged
> readline from bash implementation). This is a problem because readline
> is available even when /usr is not mounted (which is the case for many
> setup such as diskless or nfs-mounted /usr), whereas ncurses is
> installed in /usr/lib{,64}, this disallow the use of readline when /usr
> not mounted, because of this explicit linking. Is there any good reason
> doing this ?The ncurses libraries are in /lib in the clfs book I'm looking at. Bash should be able to run without /usr mounted. If you're talking about the unversioned .so symlinks in /usr/lib*, those aren't needed at runtime. The dynamic linker, /lib/ld.so will resolve to the libraries in /lib. The /usr/lib*/*.so symlinks are only strictly needed at build time. Run ldd on bash. You shouldn't see any libraries in /usr/lib there. http://cross-lfs.org/view/svn/x86_64/final-system/ncurses-64bit.html -- Dan _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
