bintools question

blz8 · 10-12-2006, 08:11 PM

Hello. I have a little question regarding bintools.

I'm trying to compile the newest glibc, just over came one hurdle (compiling & installing the newest GCC, and havign to do it agian after glibc complained to the effect of a lack of TLS support, which a simple recompile of GCC 4.1.1 did the trick with --enable-tls.)

Now I get this error:

Code:

[root@SRLINUX build]# ../glibc-2.4/configure --prefix=/usr/local/glibc2.4 --enable-addons=linuxthreads CC=/usr/local/gcc4/bin/gcc
.
.
checking for long double... yes
checking size of long double... 12
running configure fragment for sysdeps/i386/elf
checking for i386 TLS support... no
running configure fragment for nptl/sysdeps/pthread
configure: error: CFI directive support in assembler is required

Ok so I checked my assembler:

Code:

[root@SRLINUX build]# which as
/usr/bin/as
[root@SRLINUX build]# /usr/bin/as --version
GNU assembler 2.13.90.0.2 20020802

Forgetting what package as was a part of, a quick google search revealed it was part of binutils (after which I proceeded to whack my head on my desk), my current version being

Code:

[root@SRLINUX build]# rpm -qa | grep -i binutils
binutils-2.13.90.0.2-2

Ok so I went to ye olde gnu ftp and got binutils-2.17 which appears to be the newest.

* * *

Now my question is, the current binutils, which came from RPM, resides in /usr/bin/.

Is it safe to just --prefix=/usr/bin to over write the old one, or will this break anything?

* * *

P.S.

My main goal here is to install a new glibc (2.4) into it's own place in /usr/local/glibc2.4/ (just as I recently installed gcc 4.1.1 to /usr/local/gcc4/), where as old glibc can stay where it is, so a buck load of things don't end up broken.)

I obviously had to compile the new GCC (4.1.1) with the older "gcc version 3.2.1 20020903 (prerelease)", which resides in /usr/local/bin (and for that matter /usr/bin/gcc is "cc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)", the original one that came from RH rpms a while back.

After I get glibc-2.4 installed, how can I "attach" GCC 4.1.1 to it, so that when I compile with GCC 4, it uses the newer glibc stuff instead of the old "glibc 2.2.5-44", also from RPMs from a couyple years ago?

Basically my goal is to some what moderize my aging system. I nkow I could go with a newer distro, but truth be told, I feel like i've been through a life time with my ol' faitful RH 7.3 box, put a lot of work into making it "just right" for my purposes. Hell, I even use it as my own personal email server, which does a superb job of killing spam (gotta love online black list support in sendmail, which I've updatd a month ago.)

Thanks for any and all advise. While I've learned so much since I started in linux land circa 2001, I know I still have a lot to learn. (For instance, when I get glibc sorted, I've gonna compile the newest version of my kernel for the first time... before it was either RPM or a patch.)

mmiikkee12 · 10-14-2006, 04:45 PM

Quote:

Originally Posted by blz8

Now my question is, the current binutils, which came from RPM, resides in /usr/bin/.

Is it safe to just --prefix=/usr/bin to over write the old one, or will this break anything?

You want --prefix=/usr, unless you want a /usr/bin/bin/as :-)

blz8 · 10-14-2006, 08:55 PM

yes my mistake, thats what I meant. Is it safe to overwrite the old binutils?

mmiikkee12 · 10-19-2006, 03:18 PM

Yes, I've done this before with no problems.
(Just don't remove the old ones before building. Then you won't be able to build it :P

blz8 · 10-19-2006, 06:17 PM

ok thanks for your help.

osor · 10-19-2006, 07:45 PM

Your entire project/question is in the general area of what's usually called toolchain building (or toolchain replacement). So googling toolchain might help solve any further questions. You can learn a lot about how to gracefully migrate from one toolchain to the next. There are numerous resources regarding toolchains and bootstrapping: the LFS book, the buildroot project, gentoo wiki are just off the top of my head.

osor · 10-19-2006, 07:48 PM

Quote:

Originally Posted by blz8

(For instance, when I get glibc sorted, I've gonna compile the newest version of my kernel for the first time... before it was either RPM or a patch.)

Glibc and the kernel are mutually exclusive (in order to compile newer kernels, you need newer binutils and newer gcc). Of course binutils and gcc may depend on glibc, but AFAIK the kernel should not use anything from libc.

studioj · 10-21-2006, 11:26 AM

i think when you build the new glibc you should use the latest kernel headers so your glibc has proper interface with newer kernels.