Aug 2, 2010 11:48:02 AM, [email protected] wrote: >On 08/02/2010 10:33 AM, [email protected] wrote: >>> Aug 2, 2010 10:03:02 AM, Dan wrote: >>> >>> For the sake of this discussion let's assume that basic LFS and a "no >>> frills" package users system comprise a "first build." If we update the >>> hint properly, then this build should go without a hitch. [BTW. I think >>> there may be some "stuff" to ferret out in Ch. 6 up to and including >>> GCC-4.5.0. For the first time in my LFS experience, using package users, >>> I got some depressing test results. I don't know if it has anything to >>> do with my typing or whether it's package users. I do know that the test >>> results were "lovely" when I used jhalfs.] >>> >> What Dan wrote above is where my focus is right now. From what I'm >> experiencing, there are now (as Matthias stated there would be) additional >> issues that package users packages face in LFS 6.6. For instance, the >> problem I had with localedef in chapter 6.9 (glibc) is not covered. > >You've never said what the cause of the problem was nor how you found >and fixed it. Please clue us in.
*grin* That's because I haven't figured out the cause of the problem yet -- nor the solution -- although I haven't been working on it the last few days due to family committments. >> My first thought on updating the hint is to update the walkthrough of LFS for >> package users with an emphasis on not just the correct fix, but the process >> for trouble-shooting. >> >This, I believe, is step one in updating the hint. LFS has really >changed since it was last modified. What in the "process for >trouble-shooting" do you feel the hint lacks? Okay. Here's a simple one. 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. 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. 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. >> I suspect that there may be some general solutions that could address a lot >> of the problems, but I think documenting the problems and eventual solutions >> first could be a big help. >> >I recommend that you just save those until we're ready to start drafting >the changes to the hint. As you can tell, we're still in the process of >discussing what should go in the "no frills" version. Please stay >involved in that discussion. After all, you, as a "first timer" are the >target. I can't speak for Tim, but I've read that hint so many times >that I think I know what is't supposed to say rather than what it >actually does. So your views are really valuable. For example, of course >when someone supports my view I really like it :) , the comment about >the basic LFS and hint were great. > >Good luck. Oh, please post any failures you get while you build. My goal >during my current build is to identify any new "traps" in the soon to be >LFS-6.7. > >Dan Actually, when I was talking about documenting the problems and eventual solutions, I meant that I would post my failures and how I (with help from the mailing list) solved them in whatever series of messages result. The key then is to not lose those solutions, but save them somewhere with the hope that they can be incorporated into an updated hint. I think I'm making sense, but with a four-year-old and a seven-month-old in the house -- and the resultant lack of sleep :-) -- I may be rambling. Regards, -Drew -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
