Slackware64 current gcc-4.8.1 and glibc-2.17
 

Hello Slackware users :)
I compile gcc-4.8.1 and rebuild my entire system from scratch.Yes i know i use minimal system installation but all packages build perfectly.
This is the steps and packages that i rebuild from source using new gcc-4.8.1
First i recompile all the packages/dependencies needed to rebuild my entire system.
First i recompile all packages/dependencies with gcc-4.8.0

The dependencie packages needed to rebuild my entire system
This is the build order

Second step is compiling toolchain
Build order are

Third step is to recompile again all the dependencies with new gcc-4.8.1

Four step is to recompile system packages
Build order are

Five step is to compile X
Build order are

Six step is to recompile xfce4
This is the build order

Seven step is to recompile "other" packages

And thats it.
Oh and i forget all packages are build with

Hiya Tuxbg,

This might be nice for blog post.

Oh i forget one more thing :)
I rebuild gcc with cloog and isl support
This is the SlackBuild that i create to rebuild gcc

With this net-tools now compiles perfect
This is updated SlackBuild script.I made some modifications to it

tux, in your gcc script, you hardcoded x86_64 only
why not both arches ?

Well i don't think that anybody want to try this. :)
My host is x86_64 it's not so hard to edit this script and reconfigure it to i686.
I also have create a build script for all dependencies,"system stuff",all toolchain packages,"other stuff" ,etc

Congratulation, my Bulgarian friend!

And, because, of its development model, Slackware is considered as "not easy rebuild-able from sources", and even "un-rebuild-able from sources", I suggest you to continue to develop your work and this thread is what I call "it should be sticky"!

Why? Because if we manage to have a sources tree where with execution of an "slackware.Slackbuild" of even few scripts, we have opened a great window for experimentation, i.e. "which one is better as ARCH? i486, i586 or i686?" and for even more stability for Slackware, i.e. a more simple way to resolve The Great LibPNG Problem.

Also, porting the slackware to an new ARM platform will become more easy, when we known "how to build Slackware, step-by-step".

Thank you for your support neighbour :)
Well the hardest part of that build was the build order for the packages.Especially for dependiencies

Oh one more thing
libmad is compiled with -O -fPIC because of this -fforce-mem
poppler is build with --disable-poppler-qt4

This patch is needed to build Virtualbox with gcc-4.8 and gcc-4.8.1

Здравей Йоане :)
Hello all.Now i use google-chrome.To make possible to download magnet links with transmission i need to patch xdg-open.
This is the patch that i used.

New dependencies added.ITSTOOL is needed to build gnome-doc-utils.ITSTOOL must be build before linuxdoc-tools

I hope you keep updating this because I want to rebuild my system too. :hattip:

Hm ...New dep is rsync needed to build vim :)

Ok now this is for Pat :)
This patch is needed to openssl to build with new perl-5.18 because the build fails in pod2man while trying to generate man pages from the pod files
This is the error
And patch is on attachment

Speaking of cdrtools, please get the new signing key

ftp://ftp.kernel.org/pub/linux/utils...1.0.6.tar.sign

The one in Current/source was revoked a while ago.
https://www.kernel.org/signature.html

Pray! delete this as soon as it falls into your mailbox.

Nevermind, kernel.org has version 1.06, current is 1.08.

Wow :) I didn't notice when i build lilo,the compiled binary package didn't include lilo command.
To build lilo i need dev86 and sharutils.
This is the new dep list

Hello all :) Successfully rebuild all packages with new glibc-2.18

This is an amazing project.
Apart from glibc and gcc, what other packages have you upgraded?
I finished rebuilding my base install with glibc-2.19 and kernel-headers-3.12.15. After that I followed your sum-up the LFS book chapter 6 and dependencies according to salix to get the build order.
There are a few packages that were a bit hard and some I could not or haven't tried to update.
Some examples: gdbm, texinfo, readline, python and a few others.
Could you post which versions you are using and did you use the slackbuilds or did you build/compiled it another way?
I used original slackbuilds as much as possible.

If you upgrade readline to vers 6.3 you need to rebuild bc to work correct.Well i rebuild about 230 packages.Which package versions do you neeed ?

I again rebuild my slackware the past week with the new kernel-headers. I changed the order a little bit and continued up to xorg-server-1.15 succesfully.
There are a few packages I did not update but only rebuild because the change might be to big or they gave me problems I am unable to fix, yet.
A shortlist of rebuild packages I would like to upgrade:
Of course, upgrading binutils will need a complete rebuild but I still am perfecting/improving the build order for a rebuild so I don't mind to try.
My goal is to have a way of upgrading an existing linux install (here it is Slackware) with currently available buildscript (mostly original slackbuilds I used).
Finding out what is needed for my system to work and being able to update this, if there would ever cease to be support or a big change, is a good feeling.
In the meantime I might help the developers by trying out things they did not thought users might try.

Well i build binutils 2.24,upgrade gmp to 6.0.0 ,upgrade readline to 6.3 ,texinfo to 5.2 ,xorg-server to 1.15.But you need xproto -7.25,you need to build presentproto,you need to upgrade libxcb to vers 1.10,you need to add libxshmfence-1.1 ,add dri3proto,upgrade glproto to 1.47 and then upgrade xorg-server :)

When I have build xorg-server 1.15 I upgraded/added xproto 7.0.25, glproto 1.4.17, xextproto 7.3.0, dri3proto xcb-proto 1.10, libxcb 1.10, presentproto, libxshfence, libdrm 2.4.52. Well, I am going to write up my list because it's beginning to get quite long.

What symlinks do I need to create when I update gmp to 6.0?

Seems a new rebuild is needed on my laptop with all this info.

No you don't need to create any symlinks,just upgrade the package.

Hmm, interesting.. Is there any noticeable performance gain?

Only gmp itself should be a speed-up:
https://gmplib.org/gmp6.0.html

By rebuilding your packages or even upgrading the toolchain and rebuild everything from there, I guess there will be a performance gain. If you are interested in that, you could even change the CFLAGS but I kept them standard. For me the education part is more important.

This is what I am going to try, I already build in this order but only did a rebuild for binutils and gmp. Rest is the same so this hould do the trick.
@tuxbg:
What patches did you use for binutils and gmp and did you change the slackbuild?
After this I would:
My previous rebuild had this order but used rebuilds for readline, bash, net-tools, kbd, make, texinfo, man and python instead of updates.
Do I need to alter the slackbuilds for those packages and are there newer packages you are using? I could have made some mistakes and the build-order might not be optimal. I rebuild some packages twice because they depend on eachother according to salix slapt-get dependencies.
I would also like to try out uedev or an extracted udev from a recent systemd tarball. Anyone tried this?

After this I also did a rebuild/update of xorg but I will try to improve the build-order and update even more. If I can get there, everybody can try it out, I will provide detailed steps/slackbuilds. At this point tuxbg's input would help me a lot.
I start with a 14.1 slackel-openbox 6.0 install :).

Could you post your binutils-2.24 buildscript, my attempts are unsuccesfull.
Perhaps you could also provide the slackbuilds for gmp-6.0.0a, readline-6.3 and texinfo-5.2. Unless they are no different from the official ones apart from the version.

Thanks!

I used original ones SlackBuild scripts except readline.And for binutils i use ld.gold to be my deffault not ld.bdf.

ps
Do you want to share my binutils,gmp,readline and texinfo packages ?

Ok, somehow I tried with the official slackbuild for 2.23 but with the 2.24 source, what did you edit? Removed patches, extra sed-commands?
If I manage to upgrade/rebuild my entire system again with even more upgrades, I will try the binaries on a different testbox and then I am planning on trimming down the amount of packages and setting up a repo.

GMP
BINUTILS
READLINE
TEXINFO

Excellent. Could you check the slackbuild you used for binutils, it keeps failing here. I added a sed command and removed all patches, that way the package builds but the part after the oprofile output gives errors, so I am able to get a package but did not try to install.

About SLKCFLAGS=""
I use /etc/profile and add custom flags to CFLAGS,CXXFLAGS and SLKCFLAGS

Thanks again. I will try this tonight and start rebuilding my toolchain again.

You welcome ;)

So, I am building binutils and will continue with the toolchain:

U kernel-headers-3.12.15 DONE
U glibc-2.19 DONE
R zlib-1.2.8 DONE
U file-5.17 DONE
U binutils-2.24 DONE
R oprofile-0.9.7 SKIPPED
U gmp-6.0.0a DONE
R mpfr-3.1.2 DONE
U libmpc-1.0.2-1 DONE
Create symlink:
cd /usr/lib64
ln -s libmpc.so.3 libmpc.so.2
Install gcc-gnat DONE, gcc-go SKIPPED and gcc-java SKIPPED
R gcc-4.8.2 DONE
R libtool-2.4.2 DONE
R kernel-headers BUSY
R popt
R glibc
R binutils
R oprofile
R gcc
R libtool

Any comments?
After this the base will follow.
I am using slackel openbox 6.0 and I am trying to trim down my installed packages.

EDIT: I have installed the binary packages I have build on another testbox and that way I can test them at the same time.

After rebuilding gcc with new libmpc you don't need to create symlinks to new version of that library because rebuilded version of gcc now does not need older version.

I got up to the point where I want to rebuild glibc-2.19 but when I am building, it gives an error: ld too old.

Any thought, did not have this issue when I used the slackware-current binutils rebuild version.

So I tried to compile a newer version of oprofile:

I screwed up somewhere.

Well this is because glibc cant be build with ld.gold.You need to proceed like this
In my build script of binutils i use ld.gold linker instead of ld.bfd.
Or if you want your default linker to be gold apply this patch to glibc

Thanks again.
I added the patch to glibc. Are there any problems I might get into by using ld.gold?
I use grub, so I will need to be able to rebuild that. There is no more need for oprofile if I don't use ld.bfd or is there?

Hmm, I just rebuild glibc with the patch and tried to install the package. My computer froze, so I hard-rebooted and now it hangs on the boot after mounting /sys /proc. Damn.

I guess I will go for a rebuild with the current binutils, I did not have problems there.
So glibc-2.19, binutils-2.23.52.0.1, gcc-4.8.2, kernel-headers-3.12.16 and most of the latest available libraries.

I am confused, Slackware already has GCC 4.8.2 on it

Yes, that is correct. But when you rebuild your toolchain, as these guys are, building and rebuilding gcc is part of all that. Kernel headers, binutils, gcc (and deps), libc, must all be built in a certain way, often with specific peculiarities that can vary with each individual peice of the toolchain and the version used. I've been following this thread and like the way it is progressing.

I am just wondering why are they doing that if Slackware already has it

Sooooo ... they are creating a toolchain, because they are upgrading the c library. The c library, compiler, linker/assembler, kernel headers... et al, that are used in a toolchain are tightly coupled together. To properly create a new toolchain for upgrading the c library requires that the compiler is built specifically for that c library. Soooo... they have to rebuild binutils, gcc, glibc, as well as many other packages, get the order right, discover incompatiblities, fix or find fixes for those incompatiblities, build, test, rebuild, test... I am hoping you are getting the idea that is complex, the order must be correct, get one thing wrong and you have to start again (probably from the beginning). If you have messed around with LFS, then you have dabbled in toolchain building.

I still don't get it, they aren't upgrading anything. The packages are already there!
That is why I don't get it (I know about the toolchain stuff)

@moisepedro: No, glibc-2.19 is decidedly not even in current yet. Kernel headers in Slackware are from 3.10.17, here they are using 3.12.15. binutils is also more recent version.

That is what I get for not reading the whole thread. Title says glibc 2.17 tho.

The thread's title is indeed outdated.
I will end up with:

newer:
kernel-headers 3.12.16
glibc-2.19
file-5.17
gmp-6.0.0a
libmpc-1.0.2
oprofile-0.9.9

only rebuild:
mpfr-3.1.2
binutils-2.23.52.0.1
gcc-4.8.2
zlib-1.2.8
popt-1.6

Next step is the base:
I will build it like this:
@tuxbg, could you provide me your slackbuilds for texinfo-5 and readline-6. Did you try make-4? Any difficulties you ran into with those?
What version of libtermcap are you using? It's a very old package and altering some Makefiles for the programs that depends on it by using ncurses version could make it no longer needed.

I removed the --without-termcap line in the ncurses buildscript.
Then:
Now there is no need for libtermcap. Procps can be build and probably other packages that need the library like bash and xterm as well. I will continue.

I just finished bash.
Did you upgrade gdbm? I use PhantomX's buildscript at the moment. But I am going to edit the official one instead.

EDIT:
When I finished readline, needed to symlink the libreadline.so.6 to s0.5 for bash.
Tried bash-4.3 but my cpu was constantly at max freq, so rebuild bash-4.2 instead.
Might try this one again much later.

Updates I did so far after the toolchain:
pkg-config-0.28
psmisc-22.21 with old procps-3.2.8
libcap-2.24
coreutils-8.22
flex-2.5.37
bison-3.0.2
grep-2.18
readline-6.3

Now my weekend starts, I will go cycle the cobbles of Roubaix tomorrow and the cobbles and hills of Flanders saturday. I will continue saturday evening.

I use original SLackBuild for texinfo and apply This patch

Thanks, I continued through until gettext-0.18.3.2 as well.
I am thinking about kbd-2.01 or 1.5.X version. Same thing with make-4.0 or 3.82. What did you use?