[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: GCC 3.0 status?



#include <hallo.h>
Harald Dunkel wrote on Mon Jun 25, 2001 um 08:41:35PM:

> My suggestion was to install all files and executables for gcc 3.0 
> in /opt/gcc3 instead of /usr, to make sure that the ABIs are _not_ mixed. 
> (I am using 'gcc 3.0' as the name of the whole compiler set, not just for 
> the C compiler.) There is no need to artificially rename g++ into g++-3.0
> then.

Come on people, is this a really good way to go? We have unstable, so we
should try an experiment:

- get all packages depending on the old ABI in a list
- organize a "porting party"
- recompile as many libs and as many applications as possible during the
  party (making them ready for NMU). Upload all them to a special
  location, so people can test gcc-3.0 compiled apps if they want to!
- if there are less than 50-70% ported, continue in an other party.
- when we have >> 50-70%, upload them to main and report bugs to
  remaining packages.

I know, this proposal is a bit radical, but what should we do? Some
maintainers are sleeping, we would need months to move completely to
gcc-3.0.

Gr{us,eeting}s,
Eduard.
-- 
And 1.1.81 is officially BugFree(tm), so if you receive any bug-reports
on it, you know they are just evil lies."
                     (By Linus Torvalds, Linus.Torvalds@cs.helsinki.fi)



Reply to: