Recompile ALL shared libs?

ta0kira · 06-10-2005, 08:16 PM

I've been reading over the docs for gcc 4.0.0, and they say I sould rebuild all of my shared libs after the upgrade. Does this mean ALL of them, including the ones that came with my distro? That seems like a huge amount of work to set up the sources of all of the packages to build then put the libs in the correct places...
ta0kira

perfect_circle · 06-11-2005, 04:18 AM

In slackware it's a lot of work but it's not as much as you think.
All the source comes with Slackbuild scripts that will actually compile and pack the programs. in /tmp.
then you may reinstall the packages.
If you have 3-4 days spare time and a few Gbytes of free hard disk you may recompile your whole system, but as far as I remember gcc 4.0.0 has a lot of bugs and is not ready yet. It fails to compile KDE and many consider it as a beta release for the next 4.0 version. So be patient.

Harmaa Kettu · 06-11-2005, 06:33 AM

Quote:

gcc 4.0.0 has a lot of bugs and is not ready yet. It fails to compile KDE and many consider it as a beta release for the next 4.0 version.

It also fails to compile itself with my defult optimzation settings (-O2 -march=k8 -frename-registers). It crashed with "internal consistency failure" while compiling libjava. Dropping optimization to -O1 helped.

If you want to experiment with it, install it with --prefix=/opt so it doesn't replace your stable compiler and libraries.

ta0kira · 06-13-2005, 12:49 AM

Yeah, I've had a lot of problems compiling KDE with it. I installed gcc 4.0.0 in /usr/local and I left 3.3.4 in /usr just in case. But to gcc's credit, KDE sometimes has problems compiling if it knows there is already another KDE there; when I tried to compile with alsa support it gave me undefined references from my existing libs.
ta0kira