Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-11 Thread Josef Spillner
On Friday 10 January 2003 23:24, [EMAIL PROTECTED] wrote: > Daniel Stone wrote: ... > > Wrong. libGLU is C++. > > Am I right in assuming this affects only the 3D-dependent parts > of KDE? I have a card that can't do a decent tuxracer game. It affects the parts which use some helper functions for O

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-10 Thread csj
On Fri, 10 Jan 2003 14:27:00 +1100, Daniel Stone wrote: > > [1 ] > On Fri, Jan 10, 2003 at 03:07:26AM +0100, Oswald Buddenhagen scrawled: > > that's correct. gcc 3.2 is binary compatible to gcc 2.95. only g++ is > > not. as the xfree libs are all plain c ... :-) > > Wrong. libGLU is C++. Am I r

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread Daniel Stone
On Fri, Jan 10, 2003 at 03:07:26AM +0100, Oswald Buddenhagen scrawled: > that's correct. gcc 3.2 is binary compatible to gcc 2.95. only g++ is > not. as the xfree libs are all plain c ... :-) Wrong. libGLU is C++. -- Daniel Stone <[EMAIL PROTECTED]> Developer,

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread Oswald Buddenhagen
On Fri, Jan 10, 2003 at 06:14:47AM +0800, [EMAIL PROTECTED] wrote: > On Wed, 8 Jan 2003 19:01:50 -0700, > Ivan E. Moore II <[EMAIL PROTECTED]> wrote: > > > > On Thu, Jan 09, 2003 at 02:39:30AM +0100, Mario J. Barch?in Molina wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > >

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread csj
On Wed, 8 Jan 2003 19:01:50 -0700, Ivan E. Moore II <[EMAIL PROTECTED]> wrote: > > On Thu, Jan 09, 2003 at 02:39:30AM +0100, Mario J. Barch?in Molina wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > El Wednesday 08 January 2003 23:43, Daniel Stone escribi?: > > > > > * Qt3 to

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread Nikita V. Youshchenko
> torsdagen den 9 januari 2003 00.38 skrev Doug Holland: > >> Just ran dselect, so just to warn people, the new libfam0c102 conflicts >> with the Karolina KDE3 packages. I'm holding off on updating until more >> of the pieces are in place. > > Will this mean that it will be impossible to run pac

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread Ralf Nolden
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Donnerstag, 9. Januar 2003 09:46, Karolina Lindqvist wrote: > torsdagen den 9 januari 2003 00.38 skrev Doug Holland: > > Just ran dselect, so just to warn people, the new libfam0c102 conflicts > > with the Karolina KDE3 packages. I'm holding off on

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread Matthias Wieser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 09 January 2003 09:46, Karolina Lindqvist wrote: > I will be interesting to see how many libraries there are that will give > this problem. I guess it will be any C++ library. If I understood right, these are not compatible between the t

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-09 Thread Karolina Lindqvist
torsdagen den 9 januari 2003 00.38 skrev Doug Holland: > Just ran dselect, so just to warn people, the new libfam0c102 conflicts > with the Karolina KDE3 packages. I'm holding off on updating until more of > the pieces are in place. Will this mean that it will be impossible to run packages compi

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-08 Thread Ivan E. Moore II
On Thu, Jan 09, 2003 at 02:39:30AM +0100, Mario J. Barch?in Molina wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > El Wednesday 08 January 2003 23:43, Daniel Stone escribi?: > > > * Qt3 to be uploaded, built with g++3.2. > > I am building my own QT3 debs with g++3.2. Should I stop c

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-08 Thread Mario J. Barchéin Molina
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El Wednesday 08 January 2003 23:43, Daniel Stone escribió: > * Qt3 to be uploaded, built with g++3.2. I am building my own QT3 debs with g++3.2. Should I stop compiling and wait a few hours/days? - -- - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-08 Thread Doug Holland
On Wednesday 08 January 2003 03:43 pm, Daniel Stone wrote: > On Wed, Jan 08, 2003 at 03:24:02PM -0700, Doug Holland scrawled: > > Just read the story on DebianPlanet. GCC 3.2 is now the default compiler > > for Sid, meaning that the long wait for KDE 3.x to go into Sid is now > > close to an end!

Re: GCC 3.2 now becoming default compiler for Sid!!!

2003-01-08 Thread Daniel Stone
On Wed, Jan 08, 2003 at 03:24:02PM -0700, Doug Holland scrawled: > Just read the story on DebianPlanet. GCC 3.2 is now the default compiler for > Sid, meaning that the long wait for KDE 3.x to go into Sid is now close to an > end! The required steps: * libfam0 to be uploaded as libfam0c102 with

GCC 3.2 now becoming default compiler for Sid!!!

2003-01-08 Thread Doug Holland
Just read the story on DebianPlanet. GCC 3.2 is now the default compiler for Sid, meaning that the long wait for KDE 3.x to go into Sid is now close to an end! Linkage: http://www.debianplanet.org/node.php?id=895