Glibc test failure
bchaffin at programmer.net
bchaffin at programmer.net
Sun Feb 14 20:43:43 PST 2010
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.
From: Ken Moffat <zarniwhoop73 at googlemail.com>
To: LFS Support List <lfs-support at linuxfromscratch.org>
Sent: Sun, Feb 14, 2010 6:44 pm
Subject: Re: Glibc test failure
On 14 February 2010 08:18, <bchaffin at programmer.net> wrote:
> I am attempting to run the glibc tests from within my chroot environment.
> I keep getting the following errors:
> make: Entering directory `/sources/glibc-2.10.1/posix'
> /bin/sh -e globtest.sh /sources/glibc-build/ /sources/glibc-build/elf/ \
> globtest.sh: command substitution: line 32: syntax error near unexpected
> token `)'
> make: *** [/sources/glibc-build/posix/globtest.out] Error 2
> make: Target `tests' not remade because of errors.
> make: Leaving directory `/sources/glibc-2.10.1/posix'
> make: *** [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
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 ?
After tragedy, and farce, "OMG poneys!"
Unsubscribe: See the above information page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lfs-support