Bug#312585: marked as done (C++ ABI change -- xlibmesa-glu / xlibmesa-glu-dev)
Your message dated Sun, 21 Jan 2007 03:37:26 +0100
with message-id <45B2D1E6.8030309@ens-lyon.org>
and subject line Bug#312585: C++ ABI change -- xlibmesa-glu / xlibmesa-glu-dev
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: C++ ABI change -- xlibmesa-glu / xlibmesa-glu-dev
- From: Matthias Klose <doko@cs.tu-berlin.de>
- Date: Thu, 9 Jun 2005 02:37:30 +0200
- Message-id: <17063.36682.91279.450360@gargle.gargle.HOWL>
Package: xfree86
Severity: wishlist
For the upcoming C++ ABI change, one library in xfree86 (xlibmesa-glu)
has to be built for the new C++ ABI as well. At some point xfree86
will be replaced by xorg as well. Based on some experience with
spoons it doesn't look helpful to start both changes at the same
time. xlibmesa-glu is needed by a large percentage of C++ packages
(at least all of qt and kde), so I would like to see an xlibmesa-glu
built for the new ABI early during the C++ ABI change (i.e. build
xfree86 a last time explicitely with gcc-3.3, and xlibmesa-glu with
g++-3.4 or g++-4.0). This is one proposal, obviously wanting to
smooth the C++ ABI change. I'm happy about any other proposal which
eases the change for both.
--- End Message ---
--- Begin Message ---
The C++ ABI transition occurred a while ago, no need to bother anymore
trying to make it smooth :) Closing.
Brice
--- End Message ---
Reply to: