[3917] in Release_7.7_team
keeping gcc 2.95 around
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Tue Jul 8 17:28:15 2003
Message-Id: <200307082128.h68LSCmT015523@dit.mit.edu>
To: gnu@MIT.EDU
cc: alexp@MIT.EDU, release-team@MIT.EDU
Date: Tue, 08 Jul 2003 17:28:12 -0400
From: Alex T Prengel <alexp@MIT.EDU>
I've run into a number of instances, both on Sun and Linux, and particularly
in C++ code, where libraries built with gcc/g++ 2.95 or older won't link
against binaries or other libraries built with newer gcc/g++ 3.x versions-
typically there are many compiler errors complaining about undefined symbols.
In the cases I've run into, rebuilding everything from source with the
newest gcc/g++ 3.x makes the problem go away. But this sure is painful
to users and not always posssible if source is not available.
I don't know what upgrade plans there are for gcc/g++ in the gnu locker, but
given these issues could we keep 2.95 around, either by putting it in a
locker called something like gnu-old, gcc-2.95 or whatever, or saving a
copy in the existing locker and calling it something like gcc-2.95?
This gets a bit beyond my depth- but if there's another way to deal with
this with something like extra "glue" compatibility libraries such that
linking again them too would supply the undefined symbols to make the
new compilers happy, that would be fine with me- I don't know if that's
doable or not.
Alex
