LFS 6.5 chapter 8.3.1
I started over from scratch. I have captured log files of everything. I ran tests on everything and captured all those tests. Everything was going along nicely. In chapter 6.4 I used: chroot $LFS /tools/bin/env -i \ HOME=/root TERM=$TERM PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash --login +h compiled and installed everything. I skipped over chapter 6.60 stripping. I did use logout from chapter 6.60 and in chapter 6.61 I used: chroot $LFS /usr/bin/env -i \ HOME=/root TERM=$TERM PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin \ /bin/bash --login to log back in completed chapter 7 completed chapter 8.2 chapter 8.3.1 ran tar -jxvf linux-2.6.30.2.tar.bz2 cd linux-2.6.30.2 then ran make mrproper and got this error message: make: gcc: Command not found What happened? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On 12/03/2009 03:44 AM, stosss wrote: I started over from scratch. I have captured log files of everything. I ran tests on everything and captured all those tests. Everything was going along nicely. make: gcc: Command not found What happened? readelf -l /usr/bin/gcc | grep interpret What's the result? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On Thu, Dec 3, 2009 at 3:59 AM, Chris Staub ch...@beaker67.com wrote: On 12/03/2009 03:44 AM, stosss wrote: I started over from scratch. I have captured log files of everything. I ran tests on everything and captured all those tests. Everything was going along nicely. make: gcc: Command not found What happened? readelf -l /usr/bin/gcc | grep interpret What's the result? readelf: Error: '/usr/bin/gcc': No such file So I probably did something wrong and changing my path when logging out and back revealed that? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On 12/03/2009 04:04 AM, stosss wrote: On Thu, Dec 3, 2009 at 3:59 AM, Chris Staubch...@beaker67.com wrote: readelf -l /usr/bin/gcc | grep interpret What's the result? readelf: Error: '/usr/bin/gcc': No such file So I probably did something wrong and changing my path when logging out and back revealed that? So, does /usr/bin/gcc not even exist? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On Thu, Dec 3, 2009 at 4:10 AM, Chris Staub ch...@beaker67.com wrote: On 12/03/2009 04:04 AM, stosss wrote: On Thu, Dec 3, 2009 at 3:59 AM, Chris Staubch...@beaker67.com wrote: readelf -l /usr/bin/gcc | grep interpret What's the result? readelf: Error: '/usr/bin/gcc': No such file So I probably did something wrong and changing my path when logging out and back revealed that? So, does /usr/bin/gcc not even exist? No, so, where did I make my mistake? I have been looking around and things seem to be there. Did I screw up and make my LFS associated to the host? Which means I get to start over again? I am learning a lot and eventually I will get it right. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On 12/03/2009 04:15 AM, stosss wrote: On Thu, Dec 3, 2009 at 4:10 AM, Chris Staubch...@beaker67.com wrote: On 12/03/2009 04:04 AM, stosss wrote: readelf: Error: '/usr/bin/gcc': No such file So I probably did something wrong and changing my path when logging out and back revealed that? So, does /usr/bin/gcc not even exist? No, so, where did I make my mistake? I have been looking around and things seem to be there. Did I screw up and make my LFS associated to the host? Which means I get to start over again? I am learning a lot and eventually I will get it right. If /usr/bin/gcc does not exist, then clearly GCC was not installed, most likely because you missed make install in Chapter 6 GCC or somehow skipped the whole page. Of course there are other possible causes (especially if you are somehow deviating from the book), but at this point there's really no way to tell... -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On Thu, Dec 3, 2009 at 4:26 AM, Chris Staub ch...@beaker67.com wrote: On 12/03/2009 04:15 AM, stosss wrote: On Thu, Dec 3, 2009 at 4:10 AM, Chris Staubch...@beaker67.com wrote: On 12/03/2009 04:04 AM, stosss wrote: readelf: Error: '/usr/bin/gcc': No such file So I probably did something wrong and changing my path when logging out and back revealed that? So, does /usr/bin/gcc not even exist? No, so, where did I make my mistake? I have been looking around and things seem to be there. Did I screw up and make my LFS associated to the host? Which means I get to start over again? I am learning a lot and eventually I will get it right. If /usr/bin/gcc does not exist, then clearly GCC was not installed, most likely because you missed make install in Chapter 6 GCC or somehow skipped the whole page. Of course there are other possible causes (especially if you are somehow deviating from the book), but at this point there's really no way to tell... Okay? Lets say you are right that I missed installing GCC. I will go with that, but now I have a question. Did everything get built using GCC on the host? If it did then this entire LFS build is toast. That would mean without the host it won't work. Right? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On 12/03/2009 04:32 AM, stosss wrote: On Thu, Dec 3, 2009 at 4:26 AM, Chris Staubch...@beaker67.com wrote: On 12/03/2009 04:15 AM, stosss wrote: If /usr/bin/gcc does not exist, then clearly GCC was not installed, most likely because you missed make install in Chapter 6 GCC or somehow skipped the whole page. Of course there are other possible causes (especially if you are somehow deviating from the book), but at this point there's really no way to tell... Okay? Lets say you are right that I missed installing GCC. I will go with that, but now I have a question. Did everything get built using GCC on the host? If it did then this entire LFS build is toast. That would mean without the host it won't work. Right? If you need to ask that, you are *really* not paying attention to the book. If you are in chroot, you cannot possibly be using GCC (or anything else, other than the kernel of course) from the host - you are using what's in /tools (assuming of course you didn't do something dumb like cp programs from the host into $LFS). So you've been building everything with GCC in /tools, which should probably work (as the specs file was adjusted so everything else should hopefully be linked correctly) so you *might* be able to simply add /tools/bin back to the $PATH and redo Chapter 6 GCC. Of course, that's assuming GCC is the only thing missing...if it were me I'd just start from the beginning (if GCC is missing, what else might be?) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
Am Donnerstag 03 Dezember 2009 10:32:56 schrieb stosss: Did everything get built using GCC on the host? If it did then this entire LFS build is toast. Well, if you compiled _anything_ successfully and don't have a working gcc in your chroot environment, the question is, how could you use the host's gcc at all? Could something be wrong with your working environment? Something from the host sys bind-mounted into the chroot? Do a cat /proc/mounts to be sure. If anything beyond dev, devpts, shm, proc, sysfs is mounted to $LFS this is mighty suspicious [0] Or maybe you chroot'ed to the wrong place (and thus messed up your host maybe?). Maybe LFS isn't set? You can get clarity if you check the creation dates of your host's gcc, for example ls -l `which gcc` on your host. Cheers, Jan -- [0] http://www.linuxfromscratch.org/lfs/view/stable/chapter06/kernfs.html -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
Okay. I am starting over -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
On Thu, 3 Dec 2009 03:44:43 -0500 stosss sto...@gmail.com wrote: I started over from scratch. I have captured log files of everything. I ran tests on everything and captured all those tests. Everything was going along nicely. In chapter 6.4 I used: chroot $LFS /tools/bin/env -i \ HOME=/root TERM=$TERM PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash --login +h compiled and installed everything. I skipped over chapter 6.60 stripping. I did use logout from chapter 6.60 and in chapter 6.61 I used: chroot $LFS /usr/bin/env -i \ HOME=/root TERM=$TERM PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin \ /bin/bash --login to log back in completed chapter 7 completed chapter 8.2 chapter 8.3.1 ran tar -jxvf linux-2.6.30.2.tar.bz2 cd linux-2.6.30.2 then ran make mrproper and got this error message: make: gcc: Command not found What happened? It's radher hard to figure out what could cause such a mistake (without actually seeing the filesystem), but a misplaced --prefix option passed to the GCC configure is my likeliest bet. Upon entering the chroot enviroment did you do set +h? Or do you have it in bash startup files? It also might be informative if you do readelf -l /bin/bash | grep interpet or on some other arbitrary executable (if you still have the old chroot). And if all other options fail: find / -iname \*gcc\* :) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
2009/12/3 stosss sto...@gmail.com: I started over from scratch. I have captured log files of everything. I ran tests on everything and captured all those tests. Everything was going along nicely. Apart from what others have said, I find it useful to log what got installed. I think the book sketches this out, but basically: touch a known filename before you begin the install run the install command(s) run something like find / -xdev -xtype f -newer the-known-filename \ | grep -v /proc | grep -v /var/log | grep -v /sys \ | sort your-install-log This doesn't catch everything - sometimes headers or docs are older than the file used for testing - but it's usually good enough to check that *something* got installed, or to later check which package installed a file. You might want to exclude other directories too. NB - if you ever need to uninstall a package after an error in your script, treat this list of files with extreme caution (e.g it contains directory names that had already been created but were updated during the install). HTH ĸen -- After tragedy, and farce, OMG poneys! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.3.1
stosss wrote:
Okay. I am starting over
I've been doing professional software development, including
high reliability and availability stuff (telecommmunications
equipment) since 1982. I had to restart my first build, too.
Moral: Don't feel badly about it. It's a lengthy process which
is easy to screw up.
One of the easiest to screw up (and which bit me) was the necessity
to leave and re enter the chroot environment. If you don't get it
just right going back in, then you wind up with a hosed system.
If you need to start over again, be SURE that you have unmounted
everything from the chroot, and don't delete anything until after
you have exited the chroot. I recommend a reboot. You can kill
/dev in your host environment if it is still mounted in the chroot,
even if you have exited the chroot, without an unmount. If you
do this, then your host may be hosed as well.
So, if you decide to start over and delete everything so you can
go from scratch I recommend unmounting, exiting the chroot, and
rebooting for good measure.
Of course, if you use a VM or a LiveCD as your host, then you
are ok.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
