binutils-exp.xml 1.2 KB

1234567891011121314151617181920212223242526272829303132333435
  1. <sect2>
  2. <title>Command explanations</title>
  3. <para>
  4. <userinput>make -e:</userinput> The -e parameter tells make that
  5. environment variables take precedence over variables defined in the
  6. Makefile file(s). This is needed in order to successfully link binutils
  7. statically.
  8. </para>
  9. <para>
  10. <userinput>--disable-nls:</userinput> This option disabled
  11. internationalization (also known as i18n). We don't need this for our
  12. static programs and nls often causes problems when you're linking
  13. statically.
  14. </para>
  15. <para>
  16. <userinput>LDFLAGS=-all-static:</userinput> Setting the variable LDFLAGS
  17. to the value -all-static causes binutils to be linked statically.
  18. </para>
  19. <para>
  20. <userinput>tooldir=$LFS/usr:</userinput> Normally, the tooldir (the
  21. directory where the executables from binutils end up in) is set to
  22. $(exec_prefix)/$(target_alias) which expands into, for example,
  23. /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
  24. need this target specific directory in $LFS/usr. That setup would be used
  25. if the system was used to cross-compile (for example
  26. compiling a package on the Intel machine that generates code that can be
  27. executed on Apple PowerPC machines).
  28. </para>
  29. </sect2>