Re: Glibc test failure
343 MB of RAM is not enough. Unless you got about 2 GB of swap, expect all kind of errors here and there and a failure at the end. I don't know the exact amount of virtual memory required, but 2.5 GB has been the minimum over here to get the work done. Dominic. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Glibc test failure
I am attempting to run the glibc tests from within my chroot environment. I keep getting the following errors: make[2]: Entering directory `/sources/glibc-2.10.1/posix' /bin/sh -e globtest.sh /sources/glibc-build/ /sources/glibc-build/elf/ \ ld-linux.so.2 globtest.sh: command substitution: line 32: syntax error near unexpected token `)' make[2]: *** [/sources/glibc-build/posix/globtest.out] Error 2 make[2]: Target `tests' not remade because of errors. make[2]: Leaving directory `/sources/glibc-2.10.1/posix' make[1]: *** [posix/tests] Error 2 make[1]: Target `check' not remade because of errors. make[1]: Leaving directory `/sources/glibc-2.10.1' make: *** [check] Error 2 Before and between these sections, everything else compiled fine. The initial building of glibc was error free,but the test portion keeps failing. This is my first time with LFS. I am using Book 6.5 What could be causing this? Thanks for any advice. I'll take it.:) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Glibc test failure
I did this command. It worked fine: cp -v ../glibc-2.10.1/iconvdata/gconv-modules iconvdata This is the command it fails on: make -k check 21 | tee glibc-check-log And here are the results of the final command if I issue it: make[2]: *** [posix/tests] Error 2 make[2]: *** [check]Error 2 -Original Message- From: stosss sto...@gmail.com To: LFS Support List lfs-support@linuxfromscratch.org Sent: Sun, Feb 14, 2010 3:33 am Subject: Re: Glibc test failure I am attempting to run the glibc tests from within my chroot environment. I keep getting the following errors: make[2]: Entering directory `/sources/glibc-2.10.1/posix' /bin/sh -e globtest.sh /sources/glibc-build/ /sources/glibc-build/elf/ \ ld-linux.so.2 globtest.sh: command substitution: line 32: syntax error near unexpected token `)' make[2]: *** [/sources/glibc-build/posix/globtest.out] Error 2 make[2]: Target `tests' not remade because of errors. make[2]: Leaving directory `/sources/glibc-2.10.1/posix' make[1]: *** [posix/tests] Error 2 make[1]: Target `check' not remade because of errors. make[1]: Leaving directory `/sources/glibc-2.10.1' make: *** [check] Error 2 Before and between these sections, everything else compiled fine. The initial building of glibc was error free,but the test portion keeps failing. This is my first time with LFS. I am using Book 6.5 What could be causing this? Did you do this yet? cp -v ../glibc-2.10.1/iconvdata/gconv-modules iconvdata make -k check 21 | tee glibc-check-log grep Error glibc-check-log After doing this you will know if you have a problem. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Glibc test failure
I did this command. It worked fine: cp -v ../glibc-2.10.1/iconvdata/gconv-modules iconvdata This is the command it fails on: make -k check 21 | tee glibc-check-log And here are the results of the final command if I issue it: make[2]: *** [posix/tests] Error 2 make[2]: *** [check]Error 2 what about this grep Error glibc-check-log You will probably see an expected (ignored) failure in the posix/annexc test. In addition the Glibc test suite is somewhat dependent on the host system. This is a list of the most common issues: * The nptl/tst-cancel1 test will fail when using the 4.1 series of GCC. * The nptl/tst-clock2 and tst-attr3 tests sometimes fail. The reason is not completely understood, but indications are that a heavy system load can trigger these failures. * The math tests sometimes fail when running on systems where the CPU is not a relatively new genuine Intel or authentic AMD processor. * If you have mounted the LFS partition with the noatime option, the atime test will fail. As mentioned in Section 2.4, “Mounting the New Partition”, do not use the noatime option while building LFS. * When running on older and slower hardware or on systems under load, some tests can fail because of test timeouts being exceeded. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Glibc test failure
On Sun, Feb 14, 2010 at 12:29 PM, stosss sto...@gmail.com wrote: You will probably see an expected (ignored) failure in the posix/annexc test. In addition the Glibc test suite is somewhat dependent on the host system. This is a list of the most common issues: In other words: * posix/annexc ALWAYS fails, and it is ignored. So you can ignore that test. * nptl/tst-cancel1 fails with GCC 4.1.*, but only LFS 6.3 uses that, so that shouldn't fail if you use more recent GCC versions. * nptl/tst-(cpu)clock2 and tst-attr3 fail probably because of high system load, but it could be for other reasons. * You may see some math tests fail if you are not using a recent Intel or AMD processor (ie: if you are using Cytrix or VIA or maybe a old Intel or AMD processor) * If you mount the LFS partition with noatime, the atime test fails, so don't use noatime when mounting the LFS partition. * Old and slow hardware can cause some tests to fail because of timeouts being exceeded on these tests. So, if you see any errors that are not the ones I mentioned when you use grep Error glibc-check-log, you have a big problem. Bchaffin, please post the full results of grep Error glibc-check log for us. -- William Immendorf The ultimate in free computing. Messages in plain text, please, no HTML. -- Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Glibc test failure
On 14 February 2010 08:18, bchaf...@programmer.net wrote: I am attempting to run the glibc tests from within my chroot environment. I keep getting the following errors: make[2]: Entering directory `/sources/glibc-2.10.1/posix' /bin/sh -e globtest.sh /sources/glibc-build/ /sources/glibc-build/elf/ \ ld-linux.so.2 globtest.sh: command substitution: line 32: syntax error near unexpected token `)' make[2]: *** [/sources/glibc-build/posix/globtest.out] Error 2 make[2]: Target `tests' not remade because of errors. make[2]: Leaving directory `/sources/glibc-2.10.1/posix' make[1]: *** [posix/tests] Error 2 This looks worryingly similar to your earlier post without a subject (syntax error on the line DL=...). I use the expression worryingly both because sh syntax errors in the book are uncommon, and also because you *apparently* got past that earlier problem after Bruce gave you some advice on debugging the error, but the list has no idea _how_ you got past that problem. Sometimes, it is worth recording solutions, so that if someone else repeats the problem they can find the solution. I don't know if this is one of those cases. Looking at repeated problems apparently stemming from bash in chroot, I start to wonder if your version of bash in /tools is somehow broken (I can remember having that sort of problem in cross-lfs, but that was specific to cross-compiling), or else if you have somehow omitted or miscreated the /bin/bash - /tools/bin/bash or /tools/bin/sh - bash symlinks, although it seems unlikely those would do this. You said you were using 6.5. Is this 64-bit or 32-bit, and what is your host system ? ĸen -- After tragedy, and farce, OMG poneys! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Glibc test failure
I got past the DL= and similar errors by realizing those commands seemed to be extraction/substitutions. I pulled the command itself from the the script and ran it directly from a prompt to extract the information the script was looking for and used that information directly in the command that needed it, rather than relying on the substitution. In considering all your thoughts and my own observations, I am beginning to suspect a bad bash rather than a problem with the book. I am building 32 bit. My host system is a 1.6 Ghz. Pentium 4 with 343 MB of available RAM. I am running Fedora 10 as the current OS. -Original Message- From: Ken Moffat zarniwhoo...@googlemail.com To: LFS Support List lfs-support@linuxfromscratch.org Sent: Sun, Feb 14, 2010 6:44 pm Subject: Re: Glibc test failure On 14 February 2010 08:18, bchaf...@programmer.net wrote: I am attempting to run the glibc tests from within my chroot environment. I keep getting the following errors: make[2]: Entering directory `/sources/glibc-2.10.1/posix' /bin/sh -e globtest.sh /sources/glibc-build/ /sources/glibc-build/elf/ \ ld-linux.so.2 globtest.sh: command substitution: line 32: syntax error near unexpected token `)' make[2]: *** [/sources/glibc-build/posix/globtest.out] Error 2 make[2]: Target `tests' not remade because of errors. make[2]: Leaving directory `/sources/glibc-2.10.1/posix' make[1]: *** [posix/tests] Error 2 This looks worryingly similar to your earlier post without a subject (syntax error on the line DL=...). I use the expression worryingly both because sh syntax errors in the book are uncommon, and also because you *apparently* got past that earlier problem after Bruce gave you some advice on debugging the error, but the list has no idea _how_ you got past that problem. Sometimes, it is worth recording solutions, so that if someone else repeats the problem they can find the solution. I don't know if this is one of those cases. Looking at repeated problems apparently stemming from bash in chroot, I start to wonder if your version of bash in /tools is somehow broken (I can remember having that sort of problem in cross-lfs, but that was specific to cross-compiling), or else if you have somehow omitted or miscreated the /bin/bash - /tools/bin/bash or /tools/bin/sh - bash symlinks, although it seems unlikely those would do this. You said you were using 6.5. Is this 64-bit or 32-bit, and what is your host system ? ĸen -- After tragedy, and farce, OMG poneys! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Glibc test failure
Stop top posting! That is against the rules on the LFS lists and it won't be tolerated. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
GLibC Test Failure OR malloc/mtrace
Many test of GLibC fails. This is libio/fopenloc, and a lot of posix. About other don't know, I this that it is enough. The reason is missing of malloc/mtrace file (as make check writes). What should I do? How can I fix it? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GLibC Test Failure OR malloc/mtrace
developerman wrote: Many test of GLibC fails. This is libio/fopenloc, and a lot of posix. About other don't know, I this that it is enough. The reason is missing of malloc/mtrace file (as make check writes). What should I do? How can I fix it? Can you show what the error is, without the error message we can't help you. -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GLibC Test Failure OR malloc/mtrace
developerman wrote: Many test of GLibC fails. This is libio/fopenloc, and a lot of posix. About other don't know, I this that it is enough. The reason is missing of malloc/mtrace file (as make check writes). What should I do? How can I fix it? Can you show what the error is, without the error message we can't help you. Make has written that malloc/mtrace not found. -- -- [EMAIL PROTECTED] [EMAIL PROTECTED] LFS User # 2577 Registered Linux User # 299986 -- - ! http://so.yandex.ru/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GLibC Test Failure OR malloc/mtrace
On Tue, 14 Jun 2005, Jim Gifford wrote: developerman wrote: Many test of GLibC fails. This is libio/fopenloc, and a lot of posix. About other don't know, I this that it is enough. The reason is missing of malloc/mtrace file (as make check writes). What should I do? How can I fix it? Can you show what the error is, without the error message we can't help you. mtrace errors are usually caused by a broken perl installation. Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
