glibc-exp.xml 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142
  1. <sect2>
  2. <title>Command explanations</title>
  3. <para><userinput>sed 's%\$(PERL)%/usr/bin/perl%'
  4. malloc/Makefile.backup &gt; malloc/Makefile:</userinput> This sed command
  5. searches through <filename>malloc/Makefile.backup</filename> and
  6. converts all occurrences of <filename>$(PERL)</filename> to
  7. <filename>/usr/bin/perl</filename>. The output is then written to the
  8. original <filename>malloc/Makefile.in</filename> which is used during
  9. configuration. This is done because Glibc can't autodetect perl since
  10. it hasn't been installed yet.</para>
  11. <para><userinput>sed 's/root/0' login/Makefile.backup &gt;
  12. login/Makefile:</userinput> This sed command replaces all occurrences of
  13. <filename>root</filename> in <filename>login/Makefile.backup</filename>
  14. with 0. This is because we don't have glibc on the LFS system yet, so
  15. usernames can't be resolved to their user id's. Therefore, we replace
  16. the username root with user id 0.</para>
  17. <para><userinput>--enable-add-ons:</userinput> This enables the add-on that
  18. we install with Glibc: linuxthreads</para>
  19. <para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the
  20. pt_chown program to be installed in the /usr/bin directory.</para>
  21. <para><userinput>echo "cross-compiling = no" &gt; configparms:</userinput>
  22. We do this because we are only building for our own system. Cross-compiling
  23. is used, for instance, to build a package for an Apple Power PC on an
  24. Intel system. The reason Glibc thinks we're cross-compiling is that it
  25. can't compile a test program to determine this, so it automatically defaults
  26. to a cross-compiler. Compiling the test program fails because Glibc hasn't
  27. been installed yet.</para>
  28. <para><userinput>exec /bin/bash:</userinput>This command will
  29. start a new bash shell which will replace the current shell. This is
  30. done to get rid of the "I have no name!" message in the command
  31. prompt, which was caused by bash's inability to resolve a userid to
  32. a username (which in turn was caused by the missing Glibc
  33. installation).</para>
  34. </sect2>