glibcのビルド
普通の./configureのやり方と異なっている
Configuring and compiling GNU Libc
==================================GNU libc cannot be compiled in the source directory. You must build it
in a separate build directory. For example, if you have unpacked the
glibc sources in `/src/gnu/glibc-2.4', create a directory
`/src/gnu/glibc-build' to put the object files in. This allows
removing the whole build directory in case an error occurs, which is
the safest way to get a fresh start and should always be done.From your object directory, run the shell script `configure' located
at the top level of the source tree. In the scenario above, you'd type$ ../glibc-2.4/configure ARGS...
Please note that even though you're building in a separate build
directory, the compilation needs to modify a few files in the source
directory, especially some files in the manual subdirectory.
そして、こんなん出た。
checking installed Linux kernel header files... 2.0.10 or later
/usr/local since this might make your system totally unusable.
We strongly advise to use a different prefix. For details read the FAQ.
If you really mean to do this, run configure again using the extra
parameter `--disable-sanity-checks'.
それに対する答えはこれか。
2.3. How should I avoid damaging my system when I install GNU libc?
{ZW} If you wish to be cautious, do not configure with --prefix=/usr. If
you don't specify a prefix, glibc will be installed in /usr/local, where it
will probably not break anything. (If you wish to be certain, set the
prefix to something like /usr/local/glibc2 which is not used for anything.)
