glibc-2.3.2 (Chapter 5) is confused by earlier errors

Brett lfs at brettscaife.org
Tue Nov 18 22:51:12 PST 2003


Greg

I'm afraid this is turning into a bit of a saga...

> From this, I think we can deduce that your problem is related to
> the "echo" command or perhaps your shell. Hold on...   Yep,
> confirmed. I just reproduced the problem in my copy of the "ash"
> shell.
> 
> What is your "/bin/sh" symlink pointing to? What is your running
> shell at the time of building glibc?
> 
> Perhaps, changing your /bin/sh symlink to point to bash should do
> the trick. Please let us know if it solves the problem.

My symlink already pointed to bash (I don't even have any other shells
installed). I checked the echo command and it was behaving very oddly.
I guessed that this might be due to my fiddling aound with bash (I
recompiled it and upgraded it to 2.05b from the Slackware 8.1's 2.05a.
After reinstalling the sh-utils and bash packages from Slackware I
re-built everything from binutils onwards. I got rid of the problem
with version-info.h but now get this:

--------------------

mkdir /home/lfs/glibc-build/gnu
mkdir /home/lfs/glibc-build/csu
In file included from ../include/pthread.h:1,
                 from
../linuxthreads/sysdeps/pthread/bits/libc-lock.h:23,
                 from ../sysdeps/generic/ldsodefs.h:38,
                 from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from ../sysdeps/unix/sysv/linux/init-first.c:30:
../linuxthreads/sysdeps/pthread/pthread.h:163: error: parse error
    before "__thread"
../linuxthreads/sysdeps/pthread/pthread.h:165: error: `pthread_create'
    declared as function returning a function
../linuxthreads/sysdeps/pthread/pthread.h:165: warning: function
    declaration isn't a prototype
../linuxthreads/sysdeps/pthread/pthread.h:166: error: parse error
    before "void"
../linuxthreads/sysdeps/pthread/pthread.h:591: error: storage class
    specified for parameter `type name'
In file included from ../linuxthreads/sysdeps/pthread/pthread.h:655,
                 from ../include/pthread.h:1,
                 from
../linuxthreads/sysdeps/pthread/bits/libc-lock.h:23,
                 from ../sysdeps/generic/ldsodefs.h:38,
                 from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from ../sysdeps/unix/sysv/linux/init-first.c:30:
../linuxthreads/sysdeps/unix/sysv/linux/bits/sigthread.h:36: error:
    storage class specified for parameter `type name'
In file included from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from ../sysdeps/unix/sysv/linux/init-first.c:30:
../sysdeps/generic/ldsodefs.h:253: warning: type defaults to `int' in
    declaration of `type name'
../sysdeps/generic/ldsodefs.h:253: error: storage class specified for
    parameter `type name'
../sysdeps/generic/ldsodefs.h:253: error: parse error before
    "_dl_load_lock"
../sysdeps/generic/ldsodefs.h:256: warning: return type defaults to
    `int'
../sysdeps/generic/ldsodefs.h:256: warning: function declaration isn't
    a prototype
../sysdeps/generic/ldsodefs.h: In function
    `__rtld_lock_define_recursive':
../sysdeps/generic/ldsodefs.h:256: error: storage class specified for
    parameter `_dl_osversion'
../sysdeps/generic/ldsodefs.h:258: error: storage class specified for
    parameter `_dl_platform'

----------------------------

I'm starting to wonder if I need to un-upgrade my host system (if
possible) and start again.

Or is there an easier way???

Brett



More information about the lfs-support mailing list