On Fri, 23 Jun 2017 14:33:35 -0400 "Isaac D. Cohen" <[email protected]> wrote:
> Hi, > > Sorry if I'm bothering everyone too much lately. I just have a short > question this time. I continued on in the book and it says to set > the variables CC, AR, and RANLIB. So I'm wondering whether that is a > one time thing (just for that compilation) or should I add them to my > .bashrc file? I wonder because the book doesn't make it clear. It > says to set those variables before compiling binutils pass 2 and then > again before compiling gcc pass 2. So it sounds like they don't need > to be permanent. But does the book mean that they should be > permanent/set before each build? Or does it mean that they should > only be set for binutils and gcc pass 2? > > Thank you very much, > Isaac D. Cohen > They are set for these builds only. If you were expected to put them in your .bashrc file, you would have been told to do this in chapter 4. The reason they are required here in the second pass is that you are no longer cross-compiling. Consequently the configuration script will expect build tools to have normal short names. Until you have completed pass 2, the only tools with such names are the ones on your host. But you want to use the cross-compiled tools you have made in pass 1, and they have long names incorporating the architecture they were built for. So you must tell the script explicitly to use those tools. -- H Russman -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
