LFS第六章Glib make check竟然找不到文件

betatoy

第六章Glib編譯成功了可是在make check的時候出現了意想不到的錯誤, 那位能幫在下看看是什麽問題. /lfs-compile/lfs-compile03/02-glibc-build/malloc/mtrace下面明明有文件的

......
Testing SHIFT_JISX0213
character map `SHIFT_JIS' is not ASCII compatible, locale not ISO C compliant
character map `BIG5' is not ASCII compatible, locale not ISO C compliant
character map `BIG5' is not ASCII compatible, locale not ISO C compliant
character map `BIG5' is not ASCII compatible, locale not ISO C compliant
character map `BIG5' is not ASCII compatible, locale not ISO C compliant
character map `test5' is not ASCII compatible, locale not ISO C compliant
character map `test6' is not ASCII compatible, locale not ISO C compliant
character map `UTF-8' is not ASCII compatible, locale not ISO C compliant
mkdir /lfs-compile/lfs-compile03/02-glibc-build/catgets/de
/lfs-compile/lfs-compile03/02-glibc-build/stdlib/test-canon2.o(.text+0x240): In function `do_prepare':
/lfs-compile/lfs-compile03/02-glibc-source/stdlib/test-canon2.c:52: warning: the use of `mktemp' is dangerous, better use `mkstemp'
/tmp/ccEdQcGw.o(.text+0x157): In function `get_null_defines':
isomac.c: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/lfs-compile/lfs-compile03/02-glibc-build/stdio-common/temptest.o(.text+0x5a): In function `main':
/lfs-compile/lfs-compile03/02-glibc-source/stdio-common/temptest.c:14: warning: the use of `tempnam' is dangerous, better use `mkstemp'
/lfs-compile/lfs-compile03/02-glibc-build/stdio-common/tst-ungetc.o(.text+0x13): In function `main':
/lfs-compile/lfs-compile03/02-glibc-source/stdio-common/tst-ungetc.c:24: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/lfs-compile/lfs-compile03/02-glibc-build/stdio-common/bug7.o(.text+0x12): In function `main':
/lfs-compile/lfs-compile03/02-glibc-source/stdio-common/bug7.c:12: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/lfs-compile/lfs-compile03/02-glibc-build/stdio-common/tst-tmpnam.o(.text+0x41): In function `main':
/lfs-compile/lfs-compile03/02-glibc-source/stdio-common/tst-tmpnam.c:32: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/lfs-compile/lfs-compile03/02-glibc-build/stdio-common/tst-gets.o(.text+0x11): In function `main':
/lfs-compile/lfs-compile03/02-glibc-source/stdio-common/tst-gets.c:30: warning: the `gets' function is dangerous and should not be used.
/lfs-compile/lfs-compile03/02-glibc-build/stdio-common/tst-fdopen.o(.text+0x13): In function `main':
/lfs-compile/lfs-compile03/02-glibc-source/stdio-common/tst-fdopen.c:26: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/bin/sh: /lfs-compile/lfs-compile03/02-glibc-build/malloc/mtrace: No such file or directory
make[2]: *** [/lfs-compile/lfs-compile03/02-glibc-build/libio/tst-fopenloc.check] Error 127
make[1]: *** [libio/tests] Error 2
make: *** [check] Error 2

linky_fan

check不过去不代表不可以用

betatoy

Glibc太重要了, check不過去我怕以後出問題啊 樓上大人幫忙啊

linky_fan

该打的补丁打了没有?

OR 你没有加个cc---->gcc的这个软连接?

look this
[code:1]

When doing the final glibc make check, I got the "malloc/mtrace: no such file or directory" error. Asking google got me some references to this mailing list, so I decided to share my experiences with you.

I've found some references to perl being linked against the system libraries, and I believe I have found why. This occurs when you ignore the cc->gcc symlink in the tools/bin directory. Both perl and util-linux use cc instead of gcc, so they will be compiled by the host's compiler. None of the messages I read really indicated a cause.

A very dirty workaround is to create a symlink /lib/ld-linux.so.2 -> /tools/lib/ld-linux.so.2, which might work if your (host) system's libraries are not much older than the libc in /tools. The symlink will be overwritten when you install glibc.

FWIW, thank you for lfs! I'm using it a lot, both to setup my development machines and to setup some linux servers. I've even setup a sparc32 nfsroot on an i586 box, using lfs and crosstool, from which I really learned a lot ;)
[/code:1]

hohoxu_hao115

楼主编lfs做什么的呢？个人应用的话或对稳定性要求不高的话，check就没必要了。我从来没check过。
P.S.:好像sir上也有人遇到过相同的问题。