[EMAIL PROTECTED] wrote:
On 7/3/06, Chris Staub <[EMAIL PROTECTED]> wrote:
You can't do that. You must use /tools. It doesn't matter what $LFS is
and what /tools points to, but it MUST be /tools.
--
i think its ok to use /tool , as long as its point to /lfs/tool
and even
/_anything_ will work, if it links to /lfs/_thesamething_
of course, argument to the configure script will be changed simulously.
use --prefix=/_thesamething_ instead of --prefix=/tools
Nope, it's not that simple. Several reasons...
1. The book tells you to use /tools
2. Everyone in the support channel will assume you use /tools
3. Too many parts of the installation instructions, including various
commands and patches, use /tools. If you use anything else, you will
also have to modify several patches
Basically, if you don't know the significance of why a certain aspect of
the book is the way it is, that by itself is reason enough to simply do
what the book says. Once you have actually learned the reasons, and have
learned how to handle the changes, you can change stuff. Of course, for
many things (like the usage of /tools in the book), once you have
learned why that specific instruction is used, you *won't* change it
because you'll realize that doing so is not a good idea.
Looks to me that you need to start learning more about the book before
going any further. You should use the book's instructions just as they
are a few times, then once you have learned how everything works you can
start experimenting. Changing stuff (including package versions) when
you don't even have a clue how most of the book works is, frankly, just
plain stupid.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
