[SOLVED] 'Program Too Old' Error When Installing glibc 2.9
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I'm trying to install glibc 2.9 using the instructions in the package but i get:
Code:
c@c-laptop:~/U-Boot/glibc-build$ sudo ../glibc-2.9/configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: running configure fragment for add-on nptl
checking sysdep dirs... sysdeps/i386/elf nptl/sysdeps/unix/sysv/linux/i386/i686 nptl/sysdeps/unix/sysv/linux/i386 sysdeps/unix/sysv/linux/i386 nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv/i386 nptl/sysdeps/unix/sysv sysdeps/unix/sysv sysdeps/unix/i386 nptl/sysdeps/unix sysdeps/unix sysdeps/posix sysdeps/i386/i686/fpu nptl/sysdeps/i386/i686 sysdeps/i386/i686 sysdeps/i386/i486 nptl/sysdeps/i386/i486 sysdeps/i386/fpu nptl/sysdeps/i386 sysdeps/i386 sysdeps/wordsize-32 sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for ranlib... ranlib
checking whether as is GNU as... yes
checking whether ld is GNU ld... yes
checking for as... as
checking version of as... 2.20, bad
checking for ld... ld
checking version of ld... 2.20, bad
checking for pwd... /bin/pwd
checking for gcc... gcc
checking version of gcc... 4.4.1, ok
checking for gnumake... no
checking for gmake... no
checking for make... make
checking version of make... 3.81, ok
checking for gnumsgfmt... no
checking for gmsgfmt... no
checking for msgfmt... msgfmt
checking version of msgfmt... 0.17, ok
checking for makeinfo... makeinfo
checking version of makeinfo... 4.13, ok
checking for sed... sed
checking version of sed... 4.2.1, ok
checking for autoconf... autoconf
checking whether autoconf works... yes
configure: error:
*** These critical programs are missing or too old: as ld
*** Check the INSTALL file for required versions.
Now here is what I have so far:
Code:
c@c-laptop:~/U-Boot/glibc-build$ which ld
/usr/local/bin/ld
cristian@cristian-laptop:~/U-Boot/glibc-build$ which as
/usr/local/bin/as
cristian@cristian-laptop:~/U-Boot/glibc-build$ ld -v
GNU ld (GNU Binutils) 2.20
cristian@cristian-laptop:~/U-Boot/glibc-build$ as -v
GNU assembler version 2.20 (i686-pc-linux-gnu) using BFD version (GNU Binutils) 2.20
These are the latest versions of the software from: hxxp://ftp.gnu.org/gnu/. I have also tried to put an older version of glibc in the hopes that my 'old' ld and as will be accepted but it was a no go (i tried 2.7 and 2.8).
I'll also state that I am running:
Code:
c@c-laptop:~/U-Boot/glibc-build$ uname -a
Linux c-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux
How come you're trying to install glibc version 2.9 when 2.10 is available in ubuntu's repositories? For some reason Ubuntu calls it libc6 instead of glibc.
Also, I'd bet that your programs are actually too new for glibc 2.9. Sometimes installers will only look for a particular version of a program, and any version that is not the same as that is reported as being too old.
Did you ever figure this out? I have the same exact problem.
Quote:
Originally Posted by cscrieciu0
Hi,
I'm trying to install glibc 2.9 using the instructions in the package but i get:
Code:
c@c-laptop:~/U-Boot/glibc-build$ sudo ../glibc-2.9/configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: running configure fragment for add-on nptl
checking sysdep dirs... sysdeps/i386/elf nptl/sysdeps/unix/sysv/linux/i386/i686 nptl/sysdeps/unix/sysv/linux/i386 sysdeps/unix/sysv/linux/i386 nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv/i386 nptl/sysdeps/unix/sysv sysdeps/unix/sysv sysdeps/unix/i386 nptl/sysdeps/unix sysdeps/unix sysdeps/posix sysdeps/i386/i686/fpu nptl/sysdeps/i386/i686 sysdeps/i386/i686 sysdeps/i386/i486 nptl/sysdeps/i386/i486 sysdeps/i386/fpu nptl/sysdeps/i386 sysdeps/i386 sysdeps/wordsize-32 sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for ranlib... ranlib
checking whether as is GNU as... yes
checking whether ld is GNU ld... yes
checking for as... as
checking version of as... 2.20, bad
checking for ld... ld
checking version of ld... 2.20, bad
checking for pwd... /bin/pwd
checking for gcc... gcc
checking version of gcc... 4.4.1, ok
checking for gnumake... no
checking for gmake... no
checking for make... make
checking version of make... 3.81, ok
checking for gnumsgfmt... no
checking for gmsgfmt... no
checking for msgfmt... msgfmt
checking version of msgfmt... 0.17, ok
checking for makeinfo... makeinfo
checking version of makeinfo... 4.13, ok
checking for sed... sed
checking version of sed... 4.2.1, ok
checking for autoconf... autoconf
checking whether autoconf works... yes
configure: error:
*** These critical programs are missing or too old: as ld
*** Check the INSTALL file for required versions.
Now here is what I have so far:
Code:
c@c-laptop:~/U-Boot/glibc-build$ which ld
/usr/local/bin/ld
cristian@cristian-laptop:~/U-Boot/glibc-build$ which as
/usr/local/bin/as
cristian@cristian-laptop:~/U-Boot/glibc-build$ ld -v
GNU ld (GNU Binutils) 2.20
cristian@cristian-laptop:~/U-Boot/glibc-build$ as -v
GNU assembler version 2.20 (i686-pc-linux-gnu) using BFD version (GNU Binutils) 2.20
These are the latest versions of the software from: hxxp://ftp.gnu.org/gnu/. I have also tried to put an older version of glibc in the hopes that my 'old' ld and as will be accepted but it was a no go (i tried 2.7 and 2.8).
I'll also state that I am running:
Code:
c@c-laptop:~/U-Boot/glibc-build$ uname -a
Linux c-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux
I had exactly the same problem and I've tryed your workaround editting the file as you say, but the problem is that when I try to run again
sh demo-powerpc-750.sh it overwrites my configure file, How have you overcome this problem?
Alter the file configure.in instead of configure.
This way the new settings will be kept when rerunning ./configure.
Quote:
Originally Posted by Ramón Frutos Sánchez
I had exactly the same problem and I've tryed your workaround editting the file as you say, but the problem is that when I try to run again
sh demo-powerpc-750.sh it overwrites my configure file, How have you overcome this problem?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.