Is it ok to install the blfs as chroot?
 

Can you install the BLFS ( beyond linux from scratch ) libraries and programs by chrooting?


I am asking because most of the instructions to install really need to be cut and paste as it was with tcl.. That and most of those scripts that need to be setup are over a page long and are very prone to typos!! It is also a little while before I will be able to get a X system running with a browser or text editor which allows for copy and paste actions into a terminal because of all the dependencies that need to be taken care of first.

Will this cause any errors as far as anything not linking correctly or not compiling??

Well.. since no one has any thoughts on this I went ahead and said " What the hell" and did it anyway..
So far I got X running and a few other things going. There is however two things for anyone else who installs this way to be aware of that I had trouble with. I actually had better success with X and a few other things by doing it this way instead of typing everything into the console by hand.
These are merely suggestions and there may be ways around it but all I wanted was to be able to get X and internet up so that I could copy + paste and download to do the rest of the install.
1. Do not configure X by chroot. Just install..
2. Do not install ALSA by chroot. Do all of it after rebooting into the system. Not like you need or could use the sound while in chroot enviroment anyway...
I had done that and found some problems regarding some of that becuase I am using a 2.6.3 kernel while the lfs system for now had a 2.4.25 kernel ... caused alot of headaches..

i did blfs in chroot to..
 

Hello,

I subscribe to the above. Just compile X in chroot but dont config it, (although someguys from the LFS IRC support channel told me that this should be possible to...).
I had some problems relating to the 'uname -r' command. This is used to determine you're current running kernel modules directory, in "/lib/modules/'uname -r'/kernel/..". When running 'uname -r' in chroot it comes with the name of the kernel of you're host system. When you are running the same kernel this shouldnt be a problem, but my host-kernel was named '2.4.23-mdk', and that caused some problem. But with a little rewriting of the blfs-install instructions everything worked out fine.
By the way similar problems may occur when running 'depmod' in chroot.

Now i am running a fully functional and very satisfying BLFS system, completely build in chroot untill i could use X and a webbrowser. So i think building blfs in chroot is very do-able..

greetings..