Re: gcc-3.4 to unstable for amd64?
John Goerzen writes:
> On Mon, May 10, 2004 at 10:41:02PM +0200, Frederik Schueler wrote:
> > I have some questions:
> >
> > 1. when does the gcc maintainer team plan to release 3.4 to unstable?
> >
> > 2. will gcc-3.4 be included in sarge?
>
> Highly doubtful.
why? I dont' see a problem to build gcc-3.4 for amd64 only (and maybe
libffi for mips/mipsel). You'll make an unnecessary extra transition
from sarge to sarge+1 with the other architectures, but that doesn't
really hurt.
> > gcc-3.4 will become default after the release, why should we not already
> > build everything with gcc-3.4, since it produces faster code?
>
> I'm not sure that performance is itself a good enough rationale to
> justify breaking from all the other archs in sid.
gcc-3.4 by itself doesn't break anything, if you don't use it. The
problem are package maintainers beginning to build with g++-3.4 and
breaking on archs they don't test, in this case hppa and m68k. Just
look at the packages in unstable depending on libgcc1 (>= 1:3.4) ...
Matthias
Reply to: