C++ incompatibilities
On Sat, Aug 07, 1999 at 14:14:51 +0200, Richard Braakman wrote:
> (Please send followups to debian-devel, not debian-devel-announce).
Please use Reply-To to make this easier.
> - Figure out what to do about C++ incompatibilities. I don't think this
> issue has been raised yet. Right now it looks like potato will be
> completely incompatible with slink for C++ programs. We can no longer
> build the slink compatibility libraries on potato systems.
Probably the easiest solution is the creation of a package that creates a
chroot()ed environment suitable for their compilation. I admit this is a
crude hack, but a solution that doesn't require chroot() is a lot more
difficult to implement (requiring several versions of glibc and
libg++/libstdc++ to coexist).
Also, we need to decide how far back we want to be compatible C++-wise.
At the moment we have the following binary packages in potato:
libc5 era
Package: libg++27
glibc2.0 era
Package: libg++272
Package: libg++2.8 [egcs 1.0.x; needed for netscape]
Package: libstdc++2.9 [egcs 1.1.x]
glibc2.1 era
Package: libstdc++2.9-glibc2.1 [egcs 1.1.x]
Package: libstdc++2.10 [gcc 2.95]
Ray
--
POPULATION EXPLOSION Unique in human experience, an event which happened
yesterday but which everyone swears won't happen until tomorrow.
- The Hipcrime Vocab by Chad C. Mulligan
Reply to: