From kde-core-devel  Sun Sep 19 14:06:35 2004
From: Leo Savernik <l.savernik () aon ! at>
Date: Sun, 19 Sep 2004 14:06:35 +0000
To: kde-core-devel
Subject: Re: [MAJOR BUG] g++ 2.95.x generates invalid code for KDE 3.3.0
Message-Id: <200409191606.47523.l.savernik () aon ! at>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=109560257629274
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1493402.oBG9Hd0FFT"

--nextPart1493402.oBG9Hd0FFT
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Sonntag, 19. September 2004 15:28 schrieb Thiago Macieira:
> Thiago Macieira wrote:
> >And I SERIOUSLY recommend that for KDE 4, gcc 2.95 is no longer supporte=
d.
>
> In light of Adrian's email, I rephrase myself: g++ 2.95 no longer
> supported, while on Linux strongly discouraged.

Why discouraged? This is the very first gross bug that I've ever encountere=
d=20
with 2.95. No need to crap it therefore. (And I would have noticed this bug=
=20
before the release had I compiled *all* packages for the betas/rcs.)

I'm willing to stay the gcc-2.95 compliance police as long as I'm using=20
gcc-2.95 (as I've already done for the 3.2 and 3.3 releases). I just have t=
o=20
do more thorough testing of the betas/rcs.

mfg
 Leo

--nextPart1493402.oBG9Hd0FFT
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBTZJ3j5jssenUYTsRAvAMAKC85N68umLMzw3P2txXEcTDPEW9gQCfYK7i
DJxSUerIYeHLuZK8t3U4Ob0=
=/W4b
-----END PGP SIGNATURE-----

--nextPart1493402.oBG9Hd0FFT--