Re: gcc 3.4: old xine-ui packages are lost?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Jochens wrote:
| On 05-Jan-08 17:06, Harald Dunkel wrote:
|
|>AFAIR the plan was to keep gcc 3.4.x at least till Sarge is
|>released. After release date the changes done for gcc-3.4
|>were supposed to be integrated into the Unstable tree.
|
|
| The amd64 porting team decided to stay with gcc-3.3 and to
| integrate the pure64 branch which uses gcc-3.3 into unstable
| after sarge is released.
This is not about pure64!
| However, Debian unstable will likely switch
| to gcc-3.4 or gcc-4.0 some time after sarge is released. So the end
| result will be an unstable archive with gcc-3.4 or gcc-4.0 after a while.
|
Gcc 4.0 introduces some big optimizer changes. See
http://gcc.gnu.org/gcc-4.0/changes.html There is a
very high risk for optimizer problems (on all
platforms).
I would expect that Unstable will change to gcc 3.4.x
for the new base compiler after Sarge release date.
The chance to introduce gcc 4.0 as the next base
compiler after release date is pretty low.
_Unfortunately_ the amd64(gcc-4.0) folks will be out
of the loop again.
I would have preferred to keep the gcc-3.4.
About the xine-ui problem: What would you suggest to
do? Should I file a bug against xine-ui?
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB4CyOUTlbRTxpHjcRAokOAKCEPgIMjPOV2a5wKZv0mlR/003rowCeP3Zf
wsv9p//2ZmUgaeUFtJVUh7I=
=XLSk
-----END PGP SIGNATURE-----
Reply to: