binutils-exp.xml 1.2 KB

123456789101112131415161718192021222324252627
  1. <sect2>
  2. <title>Command explanations</title>
  3. <para><userinput>mkdir ../binutils-build:</userinput> The installation
  4. instructions for Binutils recommend creating a separate build directory
  5. instead of compiling the package inside the source tree. So, we create a
  6. binutils-build directory and work from there.</para>
  7. <para><userinput>--disable-nls:</userinput> This option disabled
  8. internationalization (also known as i18n). We don't need this for our
  9. static programs and nls often causes problems when you're linking
  10. statically.</para>
  11. <para><userinput>LDFLAGS=-all-static:</userinput> Setting the variable LDFLAGS
  12. to the value -all-static causes binutils to be linked statically.</para>
  13. <para><userinput>tooldir=$LFS/usr:</userinput> Normally, the tooldir (the
  14. directory where the executables from binutils end up in) is set to
  15. $(exec_prefix)/$(target_alias) which expands into, for example,
  16. /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
  17. need this target specific directory in $LFS/usr. That setup would be used
  18. if the system was used to cross-compile (for example
  19. compiling a package on the Intel machine that generates code that can be
  20. executed on Apple PowerPC machines).</para>
  21. </sect2>