Re: Freeze Goals -- WAS: September release
On Sat, 17 Jul 1999, Michael Stone wrote:
>
> On Sat, Jul 17, 1999 at 03:17:01PM +0200, J.H.M. Dassen wrote:
> > On Sat, Jul 17, 1999 at 09:10:20 -0400, Michael Stone wrote:
> > > Any estimate of how many packages will break with the upgrade?
> >
> > The kernel, if one compiles it without reading the upgrade notes; no other
> > breakage is known or expected.
>
> I thought someone mentioned that the libstdc++ was going to break again.
well, i believe the word is that if you do not use STL it is still binary
compatible, but noone on gcc team really tested this so they just declared
c++ in gcc 2.95 to be binary incompatible with c++ in egcs 1.1.x
> Is that not the case? Do 2.2 kernels break, or only older kernels?
The real concern is not kernel - it is known it will break with
new aliasing code turned on. But same problem may arise with any other
package which happened to work by accident.
shortly:
1. all libstdc++ dependent packages ought to be recompiled
2. number of packages which will break is unknown
3. fix is very simple: try to recompile with -fno-strict-aliasing
OK
Reply to: