Text 5571, 63 rader
Skriven 2006-03-28 16:21:00 av Paul Rogers (1:105/360.0)
     Kommentar till en text av Maurice Kinal
Ärende: Multiple GCC versions
=============================
 PR> Going to a newer version of KDE that has patched those errors
 PR> would drag in a whole new dependency chain, more code bloat,
 PR> more unnecessary "features"--I don't want to go there.
 MK> I don't blame you.

"Aye, and there's the rub."

 MK> How about just installing a prebuilt kde that can live with
 MK> your lib versions and save a bunch of grief?  Does
 MK> compiling kde yourself make for a better system?

Yes, it knows it has a Pentium instead of a default 386 or
sometimes now a 686, and that it has MMX for graphics.  Newer
distros are built with some, from my POV, arbitrary target
hardware.  It isn't exactly easy picking your way through
compatible dependency chains.  My criterion has been
preservation of "acceptable" performance on my P-1's.  (And, no,
it's not because I liked "The Adolescence of P-1" ;-)  So this
new system has a 2.6 kernel and the troublesome libstdc++-so.6,
but the bare miminum GTK+/gdk-1.2.10 & QT-3.1.2!  There's no way
I'm going to find a compiled binary with this configuration set!
The closest I think I can get is my LFS-4.1 system--except for
the libstdc++-so.5 problem.  After the LFS base, I'm trying to
use the same package set.

 MK> Right.  That can happen.  I am sure it could be done but
 MK> why?  Compiling kde is like getting teeth pulled methinks.
 MK> Much better things for gcc to be doing.

You mean like 8hrs to compile kdelibs?  12 for kdebase, IIRC.
It just comes with the territory as far as I can see.  If I
don't want to surrender to a P-III level distro that bogs down
my P-1, I've got to do it myself.  Some stuff I'll just need to
keep back-levelled.

 PR> I'm not sure how to tread that path, or even if it would be
 PR> successful.  Is it something I should persue?  How tricky is it?
 MK> Not very.  ldd what you notice having problems and perhaps
 MK> the answer is there.  'ldd /opt/kde/bin/knotify' or
 MK> wherever it is on your particular system.

I know that wants, libstdc++-so.5, which I copied.  Hmm, well,
maybe it wants something else--I'll check.  Perhaps the
libstdc++-so.5 version of famd.

But that's not what I meant.  Obviously installing GCC-3.2.1
would suffix its libraries.  But it would switch the top-level
symlink.  What I had in mind is what I'd have to do with
--prefix, possibly suffixing the compiler, etc., to keep it from
taking over.  I want GCC-3.4.3 to be the primary compiler, and
just use 3.2.1 for KDE--hopefully picking up the so.6 libraries.
I need to keep 3.2.1 "in its place".


Paul Rogers, paulgrogers@yahoo.com                       -o)
http://www.angelfire.com/or/paulrogers                   /\\
Rogers' Second Law: Everything you do communicates.     _\_V

... Use contraceptives on every conceivable occasion
___ MultiMail/MS-DOS v0.35

---
 * Origin: The Bare Bones BBS (1:105/360)