Re: GCC 3.2 now becoming default compiler for Sid!!!
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 OpenGL (which is always underestimated for being good for 2D graphics as well). Several KDE screensavers use GLU, e.g. flux or wave. 3D acceleration is the task of Mesa, which slowly emulates all graphics operations in software unless you have DRI enabled or at least GLX for non-DRI boards. Tuxracer uses GLU, but only to a minimal extent. OpenRacer, which succeeds Tuxracer, has been C++-ized for months now. Josef -- Free operating systems. Free software. Free games.
Re: GCC 3.2 now becoming default compiler for Sid!!!
On Fri, 10 Jan 2003 14:27:00 +1100, Daniel Stone wrote: [1 text/plain; us-ascii (quoted-printable)] 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 right in assuming this affects only the 3D-dependent parts of KDE? I have a card that can't do a decent tuxracer game.
Re: GCC 3.2 now becoming default compiler for Sid!!!
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 compiled with the old gcc compiler after a while, since a new package might require, for example, libfam0c102, where an old package require libfam0 and they are not compatible? I want to keep backward compatibility, at least for a while. So I have to figure out a way out of this. Maybe statically linking libfam, is a solution, or to make a special libfam that has a library that ends up somewhere else, or has a different .so-name. I will be interesting to see how many libraries there are that will give this problem. Karolina
Re: GCC 3.2 now becoming default compiler for Sid!!!
-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 updating until more of the pieces are in place. Will this mean that it will be impossible to run packages compiled with the old gcc compiler after a while, since a new package might require, for example, libfam0c102, where an old package require libfam0 and they are not compatible? I want to keep backward compatibility, at least for a while. So I have to figure out a way out of this. Maybe statically linking libfam, is a solution, or to make a special libfam that has a library that ends up somewhere else, or has a different .so-name. I will be interesting to see how many libraries there are that will give this problem. Have fun. I'd wait until next week when (hopefully) XFree and Qt are migrated. Then recompile your stuff. At least I'll do that. And maybe until then KDE 3.1 is already in sid :-) Ralf Karolina - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+HUXTu0nKi+w1Ky8RAo36AJ9m5FLVOO0e5SnuttfNUbibBE6PSgCggnIh T2/HE/s4OGWvHfRnImu0gT4= =ImIB -END PGP SIGNATURE-
Re: GCC 3.2 now becoming default compiler for Sid!!!
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 g++3.2 (DONE). * XFree86 4.2.1-5 to be uploaded with libGLU built with g++3.2. * Qt3 to be uploaded, built with g++3.2. * KDE3.1 to trickle into sid; arts, kdelibs, kdebase, then the rest, then kdeaddons. Those steps are in order. :) -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne pgpgg6FW6zzal.pgp Description: PGP signature
Re: GCC 3.2 now becoming default compiler for Sid!!!
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! The required steps: * libfam0 to be uploaded as libfam0c102 with g++3.2 (DONE). * XFree86 4.2.1-5 to be uploaded with libGLU built with g++3.2. * Qt3 to be uploaded, built with g++3.2. * KDE3.1 to trickle into sid; arts, kdelibs, kdebase, then the rest, then kdeaddons. Those steps are in order. :) 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.
Re: GCC 3.2 now becoming default compiler for Sid!!!
-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? - -- - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Mario J. Barchéin Molina. Granada (Spain) mario AT/EN judas.2y.net - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD4DBQE+HNLT1Cm7FLLA0lcRAurmAJwLLU0a3raBjBitjip84c/VyXb0ZQCYzow3 v7tEu8p4CzhK3vMMEpj+NA== =+qUp -END PGP SIGNATURE-
Re: GCC 3.2 now becoming default compiler for Sid!!!
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 compiling and wait a few hours/days? yes...otherwise they will break when the new X packages are available. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
