Does anyone know of the reasons why gcc-3.4.3 is still in testing/ in
Slackware-current?

--
damjan

On Tue, 25 Jan 2005 05:34:50 +0100, Damjan <gdamjan@gmail.com> wrote:

>Does anyone know of the reasons why gcc-3.4.3 is still in testing/ in
>Slackware-current?

Because Pat isn't comfortable that it works well enough yet, the same as any
other package that is in /testing.


Mark Post

Mark Post wrote:
> On Tue, 25 Jan 2005 05:34:50 +0100, Damjan <gdamjan@gmail.com> wrote:
>
>
>>Does anyone know of the reasons why gcc-3.4.3 is still in testing/ in
>>Slackware-current?
>
>
> Because Pat isn't comfortable that it works well enough yet, the same as any
> other package that is in /testing.
>

Also the gcc-3.4.x series uses a completely new installation layout to
previous gcc versions so it may well take extra integration time.


--
Regards
Martin Hughes
Linux User #283064
Blessed are those who expect nothing; for they shall not be disappointed.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Tue, 25 Jan 2005 08:32:13 +0000, Martin Hughes <martin.hughes@nospamuk.thalesgroup.com> wrote:
> Also the gcc-3.4.x series uses a completely new installation layout to
> previous gcc versions so it may well take extra integration time.

I also understand GCC 3.4.x introduced yet another C++ ABI compatibility
issue... although not quite as bad as what we got going from 2.95 to
3.2.

--
Rob | If not safe,
http://rob.axpr.net | one can never be free.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFB+Tzehm6KEoOOAe0RAolXAKC3CcHf2zYgiXsX7NGaM6 m+r9x1zgCg53Ld
ldN1fJUsdIkrhrPu7LmzRKs=
=0DVJ
-----END PGP SIGNATURE-----