8

Tutorial on building whole toolchain on CentOS

view full story
linux-howto

http://stackoverflow.com – I am working on CentOS 6 machines, which has very old GCC/GlibC version. I want to build the whole glibc, binutils, gcc toolchain with latest or at least very recent versions in order to use c++11 support in latest gcc, and ld.gold in recent binutils, and possibly improvements in recent glibc. I want to put the whole toolchain in some separate directory, and not to influence any existing system files. I also want to build gcc with --sys-root so that when using the gcc, I don't need to specify -I/some/directory/include and -L/some/directory/lib or whatever other parameters. Also the generat (HowTos)

dadebian's picture
Submitted by dadebian on 02/08/2013 – Made popular on 02/08/2013

Stories similar to Tutorial on building whole toolchain on CentOS

I followed LFS doc.

I'm not quite understand why it needs 2 pass of compilation.

My guess:

We need target system's glibc, if we compile by host's gcc, it will not be able to separate with host anymore.

I've been trying to build a cross compiler for an i486 linux based system by following LFS 6.7 and I have successfully built pass 1 of all the tools. However, when I begin the processing of second pass builds the make process will revert the target back the host system (i'm using Ubuntu 10.10 in a VM environment) which is i686-pc-linux-gnu

Can anyone help me with this?

CentOS seems to bundle a new version of glibc library RPM with every release.

6.0 has glibc-2.12-1.7.el6.x86_64.rpm 6.1 has glibc-2.12-1.25.el6.x86_64.rpm 6.2 has glibc-2.12-1.47.el6.x86_64.rpm 6.3 has glibc-2.12-1.80.el6_3.5.x86_64

What is the different between the glibc versions in each of these RPMs?

When I try to compile Binutils, Glibc and Zlib using chroot on my LFS system, I get this error:

ar: error while loading shared libraries: libbfd-2.22.so: cannot open shared object file: No such file or directory

I compiled Binutils before without using chroot, the files libbfd.a, libbfd.so, libbfd-2.22.so and libbfd.la exist both in /tools/lib/ and /usr/lib/

I don't know where the compiler

Hi!

First of all, please be kind enough to bear up with my somewhat-newbie type of curiousity.

I was wondering about the rationale behind why some certain packages are included in the toolchain. This is my second LFS build and a total new set of questions are cropping up.

1. The first question is related to Perl. Why exactly is it installed in the toolchain?

So I follow directions to unpack glibc-2.11.2.tar.gz and create an adjacent "build" directory and do the usual "sh ../glibc-2.11.2/configure --prefix=...

I am updating my glibc(in CentOS 6.3) from 1.2.10 to 2.12. is there any problem regarding dependency for other tools currently install using previous version of glibc.

We have out Gentoo hosts using a binhost with

EMERGE_DEFAULT_OPTS="--getbinpkgonly --usepkgonly"

in the make.conf file so that the host only pulled down the binary hosts. All works well from that side.

I use eix to check on software versions for upgrades but have hit a problem where eix will see an available version ahead of what is available on the binserver.

removed '/home/anish/workspace/binutils-msp430/binutils-msp430/src/build/gas/config.cache' removed '/home/anish/workspace/binutils-msp430/binutils-msp430/src/build/gas/doc/Makefile' removed directory: '/home/anish/workspace/binutils-msp430/binutils-msp430/src/build/gas/doc' removed '/home/anish/workspace/binutils-msp430/binutils-msp430/src/build/gas/.gdbinit&#039