On 07/18/2010 10:06 AM, Dan McGhee wrote: > [After a completed build and a reboot] When I mounted the partition upon > which I had built jhalfs, > there was nothing on it but /jhalfs. That directory contained another > directory `jhalfs-2.3.2` Yes, it's the untarred package. It wasn't > there yesterday. > After a build yesterday, everything is fine this morning. I must have have done something wrong the first time, but I don't really know what it is although I have a strong suspicion that there was some kind of virtual mount. I've got no clue how that may have happened. > Here's how I ran jhalfs: [<added today> ...the first time] > > 1. untarred the archive in my home directory > 2. ran make and configured jhalfs > 3. su'd to lfs and ran<make mk_CHROOT> > 4. I monitored the build as it "cooked" away and reviewed the test > files as they were created. > 5. Last night after the script quit, I turned off my computer and went > to bed. > The only significant change I did to this procedure was that I ran <make> as me and not as lfs.
I did one other thing that turned out to be wrong but was not a problem. I thought I'd point it out here for clarity. When I ran jhalfs yesterday, after someone pointed out that to stop it at a certain point I needed to make BREAKPOINT=<something> Since I wanted to do Chapters 7 & 8 manually, I actually ran make BREAKPOINT=mk_CHROOT Jhalfs started Chapter 7 and to stop it I used `Ctrl-c.` I didn't realize until I thought about it this morning that using 'BREAKPOINT=' in this case was wrong. I'm not sure what the "official" terminology is, but there's a difference "make-wise" between stopping in the middle of a chapter and stopping at the end of a chapter. The jhalfs "README" calls stopping in the middle of a chapter "the last numbered target" and the end of a chapter "the end of a top-level build phase," which is the specific description, or "the appropriate mk_*target." There are two ways to stop at the end of Chapter 6: make BREAKPOINT=123-strippingagain make mk_CHROOT The numbered targets are specific sections of chapters and running make 123_strippingagain would run only the commands in Chapter 6.62 whereas make mk_CHROOT runs everything up to and including Chapter 6.62 Sorry about this long-winded explanation, but apparently there may be some people who are confused about this. Any way, my jhalfs build is now ready for me to continue on. Thanks to all who helped me on my journey. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
