John Rodenbiker wrote: > Actually, it says "Downloaded packages and patches will need to be > stored somewhere that is conveniently available throughout the entire > build." It goes on to say that a working directory will also be > required and that $LFS/sources can work for both. The text does not say > it is necessary > > As I said, I naively thought that the sources on the Live CD _would be_ > conveniently available throughout the entire build. To avoid a long > initial copy from CD and using a ton of disk space unnecessarily, I > thought it made sense to only cp and unpack tarballs and patches as > they were required and then delete them after a successful install. > > I humbly suggest that the text in 3.1 be edited to remove ambiguity and > explicitly say that all sources need to be put in $LFS/sources from the > start. >
Actually, this would probably be a good idea, but (IMO) not for this reason. Another problem is that you would likely run into problems if you compile in /tools (as some people seem to interpret the instructions) as Glibc apparently does something weird when it sees an "include" directory. We have already changed the instructions in Cross-LFS to say that you are expected to use $CLFS/sources and that doing otherwise may have unexpected results. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
