Aside from the evilness of doing binNMUs of this magnitude, I doubt a
transition that doesn't change the SONAME will work. As soon as the
new libstdc++ is installed, every c++ app on the box will instantly
break. This means if anything happens e.g. to apt during the update, the
system will
If yes, does the following approach work: Build a libstdc++5-3.3,
conflicting with libstdc++5 (including libstdc++ with the same soname)
and doing binary uploads for hppa for all libstdc++5 dependent
packages? (The same could be done for m68k, but the compatibility
argument doesn't hold as
On Wed, May 21, 2003 at 01:08:54AM +0100, Matthew Wilcox wrote:
I'm not sure it's my call to make; I can see arguments on both sides.
Having no clue about dwarf vs sjlj (or whatever), I have to trust
*someone* to make the right call. If it's clearly the right direction,
then figure out how to
On Wed, May 21, 2003 at 01:42:53AM +0200, Matthias Klose wrote:
For Debian GNU/Linux gcc-3.3 is currently configured with
--with-sjlj-exceptions
to allow a binary compatible upgrade from gcc-3.2 to gcc-3.3. The
other Debian platform, where sjlj based exceptions changed to dwarf2
On Mer, 2003-05-21 at 01:08, Matthew Wilcox wrote:
I'm not sure it's my call to make; I can see arguments on both sides.
Thats at least one of the reasons. Reputation capital is a wonderous
thing. Accept reality, you are the Linus of parisc Linux like it or not
8)
On Mer, 2003-05-21 at 01:08, Matthew Wilcox wrote:
I'm not sure it's my call to make; I can see arguments on both sides.
Thats at least one of the reasons. Reputation capital is a wonderous
thing. Accept reality, you are the Linus of parisc Linux like it or not
8)
I agree.
Dave
--
J.
[ Dropped non-Debian lists. ]
Matthew Wilcox [EMAIL PROTECTED] writes:
On the other hand, dwarf exceptions are clearly superior to sjlj.
We've never _released_ a distro compiled with 3.2 so we can break
the binary ABI without major repurcussions.
Err, no you can't. Redoing the C++
7 matches
Mail list logo
