On 08/02/2010 12:34 PM, jxa...@verizon.net wrote: > .....How do you back out of a problematic installation > to trouble-shoot? Let's say I run into a permissions problem and make install > only partially works and then spits out a bunch of errors. Obviously, the > package > is not fully installed, but there are probably some of the installed files in > the file > system now. > > I think the solution is to use the unistall_package script on the newly > installed > package and start over with that package -- unpacking a clean source tree and > investigating make.in files or makingvarious directories install > directories_before_ > starting ./configure and so forth. > You are correct in your analysis, but you don't have to go back to a clean source tree if you don't want to. If you successfully got to the "Install" script in package users, the compile is complete and satisfactory. You need only investigate and fix the cause of the failed install and run the script again. Depending on your personal preferences you can either overwrite the existing files or you can, as you suggested, run "uninstall_package $(whoami)" and remove the created log files from the home directory before running the install script again. > The hint is very good about explaining trouble-shooting, but this relatively > simple > trouble-shooting sequence eluded me for a bit; especially because with a non- > package users type of install a lot of problems seem to be caused by bad > toolchains > or not getting into the chroot environment correctly. The advice in those > cases is usually > to start over. > Whenever I've had a problem in LFS or, with the exception of install directories, in BLFS, I, myself, have always, I repeat always, been the cause of the problem. Typo. Missed command. Incomplete command. Skip a step. Mis-reading the book. My best one was reading the wrong page and entering the wrong configure switches. These mistakes encompass the two conditions you described.
If you're working in Ch. 5, it's just as easy to start from scratch as it is to try to repair one package. If it's the tool chain, start again. In Ch 6, up to and including the installation of GCC, the same principles apply. Once past GCC, if you make a mistake you just go back to the point of the offending package and start from there. > So, it seems that package users can make the installation more time-consuming, > but if one's toolchain and chroot environment are correct, problems are > easier to > back out of. > Unless there are some as yet unidentified "traps" in the changes to LFS since the hint was last updated--and the major changes are the dependencies now in the tool chain--you should just be able to "breeze through" the LFS build even with package users. In the absence of these traps, any problems you may have probably come from one of the causes I mentioned above. The only "added step" when using package users is running "install_package." Otherwise, it's exactly like building without the system. Take your time. Understand the steps. Have a good experience. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
