> In a small new partition, I started to build LFS-8.1. I had to go > through Chapter 5 and then started chapter 6, until 6.17, GMP-6.1.2. I > built this, as adviced by Bruce, with the settings for generic libraries > cp -v configfsf.guess config.guess > cp -v configfsf.sub config.sub. > Then, I copied the files libgmpxx.so.4.5.2 and libgmp.so.10.3.2 to > /usr/lib in my system. > > This allowed me to compile, as a first test, the terminal emulator > "rxvt", as Paul Rogers adviced. Now, I have the "minimal" two > independent terminals. > > The time for building the "LFS" chapters was acceptable, considering my > problem. I do not know, if this is a general "remedy" for the > misconfigured ported system, I shall see. For sure, I learned again a lot.
OK, but you can't really have total confidence in this system. Again let me suggest bugs in a system are like cockroaches: if you see one there are others hiding around. I suggest confidence very important (it's actually my major reason for using LFS instead of distros built by others!) and should be your next course of action--and you can begin this process on your laptop. Initially it's just reaing the book and making scripts. The process I have used since LFS-4.1, with enhancements since but still very much the same, is to go through each section of the book, cut and paste, and hand edit, the commands into a script for building each package. Many of the scripts for Chapter 6 will be slightly modified versions of what you make for Chapter 5. This is very much what JHALFS does, but again we learn by doing. Then you use those to rebuild your current system from scratch all over again, correcting the inevitable mistakes in the scripts as you go. But then with what you've learned, you will have a corrected compiler you are confident is building correct code. Then you can reliably reproduce the built system confidently, and much easier that typing in the commands at the shell a second time! Not only that, but this is, of course, the base from which you'll make generally minor edits from the next book to build your next system, reliably and reproducibly. Hint: Do something like naming each script with the pattern: chapter-section-package-version. Hint: If you're going to want to migrate the built systems to other boxes as you have done, then choose your build options for the "lowest common denominator" system. There is a common saying: Prepare to throw away your fist attempt. I built my first LFS system by hand, entering commands to the shell. When that was usable, then I quickly began the process above and rebuilt it. I still have all the scripts from every LFS version I've built since. Not only is there the process of building and learning to run a Linux system, but there is also a system development management process to learn. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
