LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)
-   -   'Program Too Old' Error When Installing glibc 2.9 (https://www.linuxquestions.org/questions/linux-from-scratch-13/program-too-old-error-when-installing-glibc-2-9-a-768992/)

cscrieciu0 11-13-2009 04:35 PM

'Program Too Old' Error When Installing glibc 2.9
 
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

Furthermore, my env vars contain PATH as follows:
Code:

c@c-laptop:~/U-Boot/glibc-build$ env | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

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

, which is actually:
Code:

c@c-laptop:~/U-Boot/glibc-build$ cat /etc/issue
Ubuntu 9.10 \n \l

(aka Karmic Koala with all updates applied).

What am I doing wrong?? I'm stuck!

Can anyone throw any ideas please...

BR,
/C

everest40 11-14-2009 12:47 AM

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.

everest40 11-14-2009 12:52 AM

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.

knudfl 11-14-2009 02:48 PM

Welcome to LQ.

One thing is sure, you can't mix versions not fitting together.

Either it is for U-Boot / Embedded / Cross compiling or
Linux From Scratch.

Suggest : Follow the LFS Book strictly
http://www.linuxfromscratch.org/lfs/view/6.5/

or even better CLFS , " Cross Linux From Scratch ",
if you are cross building : http://trac.cross-lfs.org/
http://www.linuxfromscratch.org/news.html

The binutils you have = version 2.20 is too new for glibc-2.9 .
Current stable binutils is 2.19.51. Some older ones : more stable.

About cross tools : The recommended / supported / maintained one
is crosstools-ng : http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool
( Updated about two weeks ago.)
.....

brownwrap 02-01-2010 02:55 PM

I can't build glibc either in LFS
 
Did you ever figure this out? I have the same exact problem.



Quote:

Originally Posted by cscrieciu0 (Post 3756244)
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

Furthermore, my env vars contain PATH as follows:
Code:

c@c-laptop:~/U-Boot/glibc-build$ env | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

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

, which is actually:
Code:

c@c-laptop:~/U-Boot/glibc-build$ cat /etc/issue
Ubuntu 9.10 \n \l

(aka Karmic Koala with all updates applied).

What am I doing wrong?? I'm stuck!

Can anyone throw any ideas please...

BR,
/C


tcicone 05-06-2010 08:49 AM

I had this problem, with using binutils-2.20.1. To get past it, I edited the configure script for glibc, and changed these lines:

case $ac_prog_version in
'') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
2.1[3-9]*)
ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
*) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;

case $ac_prog_version in
'') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
2.1[3-9]*)
ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
*) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;

to this:

case $ac_prog_version in
'') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
2.2[0-9]*)
ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
*) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;

case $ac_prog_version in
'') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
2.2[0-9]*)
ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
*) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;

AlphaBravo 05-06-2010 11:55 AM

Why are you trying to install glibc 2.9? You should use either 2.10 or 2.11. You should use LFS 6.5+

Ramón Frutos Sánchez 10-16-2010 07:54 AM

Problem editting configure file
 
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?

TimKouters 02-02-2011 10:26 AM

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 (Post 4129473)
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?



All times are GMT -5. The time now is 07:41 PM.