Installation of Glibc
Once glibc has been unpacked as usual and you have cd'ed into the
glibc-&glibc-version; directory, unpack glibc-linuxthreads inside
the glibc-&glibc-version; directory, not in /usr/src as you normally
would do.
Install Glibc by running the following commands:
mknod -m 0666 /dev/null c 1 3 &&
touch /etc/ld.so.conf &&
mkdir ../glibc-build &&
cd ../glibc-build &&
sed s/"\$(PERL)"/"\/usr\/bin\/perl"/ \
../glibc-&glibc-version;/malloc/Makefile > tmp~ &&
mv tmp~ ../glibc-&glibc-version;/malloc/Makefile &&
sed "s/root/0/" ../glibc-&glibc-version;/login/Makefile > tmp~ &&
mv tmp~ ../glibc-&glibc-version;/login/Makefile &&
../glibc-&glibc-version;/configure \
--prefix=/usr --enable-add-ons \
--libexecdir=/usr/bin &&
sed s/"cross-compiling = yes"/"cross-compiling = no"/ \
config.make > config.make~ &&
mv config.make~ config.make &&
make &&
make install &&
make localedata/install-locales
During the configure stage you will see the following warning:
configure: warning:
*** An auxiliary program is missing or too old;
*** some features will be disabled.
*** Check the INSTALL file for required versions.
This warning refers to the missing msgfmt program from the gettext
package. But there is nothing to worry about: Glib will still be
installed the same way as when msgfmt is present. It can safely be
ignored in our case.
By exiting the chroot'ed environment and re-entering it, you will be
able to get rid of the "I have no name!" message in the command prompt,
which is caused by bash's inability to resolve a userid to a username.
You don't have to exit and re-enter chroot, but it's highly recommended
to ensure a properly working bash.
Run the following commands to accomplish this:
logout
&c6-chrootcmd;