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.
In following the directions posted, I found a situation that was not covered.
The host system for this build has 'libtool' in a system wide install. Putting the switch '-disable-shared' in the ./configure kills the necessary linker function. The 'static' builds produce non-functional libs or executables.
The Ncurses-5.9 package does have a work around coded in. The './configure --help' shows it.
GCC 4.6.3 does not. Common Errors : 'gcc cannot compile', or 'no installed CLooG detected'.
The functional workaround for this :
LDFLAGS="-Wl,-rpath,/cross-tools/lib -static-libtool-libs"
As more people use GUI desktops as hosts, 'libtool' will be the silent problem that kills their build attempt. It cannot be removed without killing the GUI (...in a slow and agonizing way).
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,152
Rep:
Libtool is always,ALWAYS a major PITA.
But is there any particular reason you want to disable shared libs with ncurses and gcc?
Also note the gcc can be built without cloog/ppl ( there are configure switchs for it "--without-cloog --without-ppl") I don't use cloog as it seems to be just a very complex way of optimizing a few loops.
Yes, there is a reason for static builds of ncurses and gcc.
By the book, it is supposed to break any dependencies on the host system from carrying over to the new system.
I'm going to try it again, this time NO chroot, straight to the 'Boot' instead.
If my guess/hunch is correct, chroot + root priv. lets 'libtool' break the 'chroot jail'.
The LD_LIBRARY_PATH is hardcoded into 'libtool', apparently. No way to override it.
So everything has the path [/cross-tools] or [/tools] or [/mnt/clfs] coded into it.
The '--with-sysroot=' does not seem to be working on 'libtool'.
Host system version of 'libtool' = 2.4
The command line switches for 'gmp,mpfr,mpc,cloog,ppl' locations don't work when 'cross-compiling', according to GCC's configure & install Wiki. The developers say to use the download script included in GCC for 'gmp,mpfr,mpc'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.