Public SourceMage Discussion List

[Seth Alan Woolley <seth AT positivism.org>]

On Fri, Feb 25, 2005 at 04:11:53PM -0800, Andrew wrote:
> As a consequence though, to the end users (smgl for example), everyone who
> builds stuff from source gets the shaft. You'd get the same problems if
> you used a binary distro and then updated to 3.4 then started building
> a few things here and there, they wouldnt work and all your binary
> packages would either need to be updated (and their probably arent
> updates), or you'd have to give up using gcc 3.4 until their were. Or
> on other source distros youd have similar (if not the same) issues,
> its not really a unique to smgl problem, and unfortunatly we cant just
> make the incompatibility disappear without having to rebuild a bunch of
> stuff that was broken by it.

Keeping the old libstdc++ and possibly other libraries around, ldd'ing 
looking for dynamic links to it, collating by spell, and then recasting 
could be done in g++/FINAL instead of using a trigger.  Prompt in 
configure with a default to no unless the new and old version have their 
minor version "cut -d. -f2" not identical, delete the old libstdc++ now, 
and call the problem fixed.

Or did I miss something?

Seth

-- 
Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
Key id 00BA3AF3 = 8BE0 A72E A47E A92A 0737  F2FF 7A3F 6D3C 00BA 3AF3
http://smgl.positivism.org:11371/pks/lookup?op=get&search=0x00BA3AF3
Security Team Leader Source Mage GNU/Linux http://www.sourcemage.org

Attachment: pgp4LbyrCoChC.pgp
Description: PGP signature