Yes i bootstrap gcc.Also now i use gcc 4.9.20131027 i tried gcc 4.9.0-RC-20140411 but i can't rebuild my toolchain with that vers.I will wait for 4.9 stable vers.

I have build gcc with newest fastjar and antlr-runtime. Added a patch for fastjar-0.98 and removed all old patches.
About the bootstrap, I managed to get to finishing chapter 5 LFS and adding aaa_base, pkgtools and start compiling with the bootstrapped toolchain but things go wrong when I try to readjust to the toolchain again, what chroot commands do you use and how do you switch to the toolchain when gcc and binutils are build with the temporary toolchain?

Do you cross-compile ?
I rebuild all of my packages on the top of my system.
When i rebuild toolchain,all packages needed to build toolchain must be rebuilded.After that i rebuild my toolchain again.After that i start rebuildin all of my packages.

Currently I rebuild on top of my installation and don't boorstrap, I just replace the newly compiled packages for the toolchain and rebuild all others after that. As if I were just updating.

I am trying to use a live cd as a host. Then follow the LFS book up to end of ch5 with some changes for tar and tar-1.13. I follow this:
http://www.linuxquestions.org/questi...oolchain-3233/
but there is no post about chapter6. And using the commands from the book from ch6 and replacing creation of folders with aaa_base and adding etc and pkgtools seems to work up to where I need to readjust the toolchain again. I probably need to adjust those commands, but no idea there.

For native build you must bootstrap.

I found a patch for the binutils problem with gcc-4.9.0 here: https://bugzilla.redhat.com/show_bug.cgi?id=1087374
Glibc fails but I did not build a native gcc.
Upgrading glibc was not problem and rebuilding gcc also was possible with the official slackware.
For a native gcc-build, I suppose you need at least add --enable-bootstrap and perhaps remove the --host=.
How does your gcc native rebuild slackbuild look like?
I am trying to figure out the steps of upgrading the toolchain, glibc and binutils seems to work with the slackbuilds as they are, small changes here and there.

@hendrickxm,

Looking at the comments, I saw a lot of failures in some tests. You can try building you chain with binutils-2.24.51.0.3 or form git, as I read somewhere that the daily snapshots are being picked from the old CVS, but don't take that from granted.

From the git sources, to build just the binutils without gdb, add to your ./configure settings:
--disable-gdb \
--disable-sim \
--disable-readline \
--disable-libdecnumber \

If oprofile rebuild fail, add 'sed -i "s|SYNTHESIZE_SYMBOLS\ 1|SYNTHESIZE_SYMBOLS\ 0|g" config.hy' right before the make command.

I think libiberty is now picked from GCC and not binutils anymore...

obs: To build binutils-2.24 with the new GCC on x86_64, you now need to pass WERROR="--enable-werror=no" or it will fail.

I already am rebuilding my toolchain with gcc-4.9.0 and binutils-2.24.51.0.3 is failing, will try with your tips.
The error is with cpp and a missing minix header.
I disabled profile in gcc and I am using libiberty from binutils, it does seem that the gcc version is being used in most distros.

EDIT: binutils-2.24.51.0.3 still fails:
"/lib/cpp" fails sanity check
/lib/cpp --version gives me 4.9.0
Acoording to the config.log minix/config.h is missing.

Something is wrong with your compiler =[

binutils-2.24.51.0.3 built fine (*-2.24.51.0.3.20140127.so). Aside disabling multilib support, building libiberty from GCC and bumping the timezones for glibc (2.19); the build scripts are almost stock. I have some strange compulsion to rebuild libtool after GCC with both 1st and 2nd pass.

~$ cpp --version
cpp (GCC) 4.9.0
Copyright (C) 2014 Free Software Foundation, Inc

The minix/config.h error seems just like a warning. I don't have it here, even in the Linux headers (needed by glibc).

My slackbuilds are also almost stock.
From a stock slackware I have build and upgraded kernel-headers-3.14.1, glibc-2.19, binutils-2.24.51.0.3, gmp-6.0.0a, mpfr-3.1.2, libmpc-1.0.2.
After that gcc-4.9.0, kernel-headers again and then trying binutils.
Could you post your binutils and gcc slackbuilds, I might have missed something? Thanks.
ure
I don't make a static gcc first. Should I, I just have the --enable-bootstrap in the ./configure.
How can I speed up the slackbuild easily by only building gcc for c and c++.

After rebuilding gcc with slightly different configure options I also managed to build binutils. Glibc is now spewing an error. I will post my slackbuilds for gcc, binutils and glibc. There may be something wrong in these.

So if I understand correctly in your first post. You upgrade your toolchain after you have installed/rebuild with current toolchain all needed packages for it. After that you rebuild all those needed packages again and after that you rebuild your toolchain again and after that rebuild all packages on your system?

Step 1: install (and if wanted rebuild/upgrade some of) all packages needed for upgrading toolchain
Step 2: upgrading toolchain
Step 3: rebuilding needed packages for toolchain
Step 4: rebuilding upgraded toolchain
Step 5: rebuilding system packages

Could I get your gcc, gcc-static and glibc slackbuild please? Then I can start trying your way of upgrading the system.

@hendrickxm,

Please verify the 'sed' to install libiberty headers. It came from GCC 4.8.x and I always forget to verify if it was fixed, but 4.9 built with the headers correctly placed. mpfr cumulative patch (08) fixed some bugs, one linked to GMP 6. If you run 32bit or Alien's multilib some editing is needed...

Attached Files

	binutils.SlackBuild.txt (6.1 KB, 20 views)
	gcc.SlackBuild.txt (28.0 KB, 14 views)

Thanks, I will try building with your slackbuilds sunday evening. I am gone cycling this weekend.

For native build you must bootstarp
edit your gcc configure to
--enable-languages=c,c++,lto