Chris Staub a écrit : > [EMAIL PROTECTED] wrote: >>> >>> certainly can change instructions and versions, assuming that you >>> actually know what you're doing. However, if you do something like >>> change the location of /tools, then you clearly *do not* know what you >>> are doing. It's that simple. >>> -- >> i dont think /tools is that important, >> yes it makes things simple by agree on a common decision, >> but since i 'm using new version, i cant see the necessarity to apply >> all lfs-book patch, >> i guess thats' the real valuable point to insist on /tools, isn't it? >> >> and what if i say that i have changed to /tools and still experience >> the same problem? > > In my previous message, I did in fact list at least one *practical* > reason to use /tools (not just "because the book does"). Of course, the > real question is - why *would* you change it? There is no purpose to > doing anything different - and all the necessary work to accomodate the > differences (like modifying several patches) - for a directory name that > won't even exist in the final system. And yes, if you start completely > over and use /tools, and still have the same problem, then you may very > well be worth helping. > > And yes, most of the lfs patches are still needed. Again, if you > actually understood the build process (and you *shouldn't* be attempting > to do anything differently until *after* you have followed the book > exactly a few times and know how it works), you would know this. ok ok we go far of the problem here maybe a good question is : are you sure you have limits.h ? and if you want new version of packages why don't you use the svn book of clfs project ?
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
