| 1 | <sect2>
|
|---|
| 2 | <title>Command explanations</title>
|
|---|
| 3 |
|
|---|
| 4 | <para><userinput>mknod -m 0666 /dev/null c 1 3:</userinput> Glibc needs a
|
|---|
| 5 | null device to compile properly. All other devices will be created in the
|
|---|
| 6 | next section.</para>
|
|---|
| 7 |
|
|---|
| 8 | <para><userinput>touch /etc/ld.so.conf</userinput> One of the final steps of
|
|---|
| 9 | the Glibc installation is running ldconfig to update the dynamic loader
|
|---|
| 10 | cache. If this file isn't present Glibc will abort with an error that it
|
|---|
| 11 | can't read the file. So we create an empty file for it (the empty file
|
|---|
| 12 | will have Glibc default to using /lib and
|
|---|
| 13 | /usr/lib which is fine right now).</para>
|
|---|
| 14 |
|
|---|
| 15 | <para><userinput>sed s/"\$(PERL)"/"\/usr\/bin\/perl"/
|
|---|
| 16 | ../glibc-2.2.3/malloc/Makefile > tmp~:</userinput> This sed command
|
|---|
| 17 | searches through <filename>../glibc-2.2.3/malloc/Makefile</filename> and
|
|---|
| 18 | converts all occurances of <filename>$(PERL)</filename> to
|
|---|
| 19 | <filename>/usr/bin/perl</filename>. The output is then written to the
|
|---|
| 20 | file <filename>tmp~</filename>. This is done because Glibc can't
|
|---|
| 21 | autodetect perl since it's not installed yet at the time when we install
|
|---|
| 22 | Glibc.</para>
|
|---|
| 23 |
|
|---|
| 24 | <para><userinput>mv tmp~ ../glibc-2.2.3/malloc/Makefile:</userinput> The file
|
|---|
| 25 | <filename>tmp~</filename> is now moved back to
|
|---|
| 26 | <filename>../glibc-2.2.3/malloc/Makefile</filename>. We do this because
|
|---|
| 27 | when using sed, we can't write straight back to this file so we need to
|
|---|
| 28 | use a temporary file in between.</para>
|
|---|
| 29 |
|
|---|
| 30 | <para><userinput>sed "s/root/0" ../glibc-2.2.3/login/Makefile >
|
|---|
| 31 | tmp~:</userinput> This sed command replaces all occurances of
|
|---|
| 32 | <filename>root</filename> in
|
|---|
| 33 | <filename>../glibc-2.2.3/login/Makefile</filename> with 0. This is
|
|---|
| 34 | because as we don't have glibc on the LFS system yet, usernames can't
|
|---|
| 35 | be resolved to their user id's. Therefore, we replace the username
|
|---|
| 36 | root with the id 0. </para>
|
|---|
| 37 |
|
|---|
| 38 | <para><userinput>mv tmp~ ../glibc-2.2.3/login/Makefile:</userinput> As above,
|
|---|
| 39 | we are using a temporary file (<filename>tmp~</filename>) to store the
|
|---|
| 40 | edited Makefile and then copying it back over the original.</para>
|
|---|
| 41 |
|
|---|
| 42 | <para><userinput>--enable-add-ons:</userinput> This enables the add-on that
|
|---|
| 43 | we install with Glibc: linuxthreads</para>
|
|---|
| 44 |
|
|---|
| 45 | <para><userinput>sed s/"cross-compiling = yes"/"cross-compiling = no"/
|
|---|
| 46 | config.make > config.make~:</userinput> This time, we're replacing
|
|---|
| 47 | <filename>cross-compiling = yes</filename> with
|
|---|
| 48 | <filename>cross-compiling = no</filename>. We do this because we are
|
|---|
| 49 | only building for our own system. Cross-compiling is used, for
|
|---|
| 50 | instance, to build a package for an Apple Power PC on an Intel system.
|
|---|
| 51 | The reason Glibc thinks we're cross-compiling is that it can't compile a
|
|---|
| 52 | test program to determin this, so it automatically default to a
|
|---|
| 53 | cross-compiler. The reason for the failed program is because Glibc
|
|---|
| 54 | hasn't been installed yet.</para>
|
|---|
| 55 |
|
|---|
| 56 | <para><userinput>mv config.make~ config.make:</userinput> Again, we are moving
|
|---|
| 57 | the temporary file over the original.</para>
|
|---|
| 58 |
|
|---|
| 59 | </sect2>
|
|---|
| 60 |
|
|---|
