'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 Code:
c@c-laptop:~/U-Boot/glibc-build$ which ld Code:
c@c-laptop:~/U-Boot/glibc-build$ env | grep PATH I'll also state that I am running: Code:
c@c-laptop:~/U-Boot/glibc-build$ uname -a Code:
c@c-laptop:~/U-Boot/glibc-build$ cat /etc/issue What am I doing wrong?? I'm stuck! Can anyone throw any ideas please... BR, /C |
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.
|
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.) ..... |
I can't build glibc either in LFS
Did you ever figure this out? I have the same exact problem.
Quote:
|
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;; |
Why are you trying to install glibc 2.9? You should use either 2.10 or 2.11. You should use LFS 6.5+
|
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? |
Alter the file configure.in instead of configure.
This way the new settings will be kept when rerunning ./configure. Quote:
|
All times are GMT -5. The time now is 07:41 PM. |