[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] GCC 3.1/3.2
From:       Doug Goldstein <cardoe () gentoo ! org>
Date:       2002-07-28 22:16:16
[Download RAW message or body]

Michael Mattsson wrote:

>Just curious.  Who are you sending patches to?  Gentoo scripters, or
>independent QT/GTK developers?  
>What kind of patches are you refering to?  Gcc3.2 or kernel patches?
>Why arent any patches in the cvs tree?  How many questions can I fit
>onto one paragraph?
>
>I'm kind of confused as I thought that pretty much all gentoo related
>code were script based.  If this is not the case, then is it possible to
>get a list of gentoo specific modules that may be affected by future GCC
>upgrades?   I ask this because I tend to use the latest GCC CVS
>snapshots for my development (currently gcc 3.1.3).
>
>
>
>Michael Mattsson
>Kyrana Inc.
>michel@kyrana.com
>
>
>
>  
>
>>-----Original Message-----
>>    
>>
>
>  
>
>>3.2 is labeled by GNU to be 100% multi-vender compliant with 
>>the C++ ABI 
>>now. Which is the core prob with the new gcc releases. By skipping 
>>straight to 3.2 we'll avoid 2 problem transitions.. 1 from 
>>2.95 to 3.1 
>>and then from 3.1/3.1.1 to 3.2 instead we'll have 2.95 to 
>>3.2. As one of 
>>the gcc-3.1/gcc-3.2 Gentoo guys I support this plan (was one 
>>of the ones 
>>calling for it among the devs) and I'm working hard with all 
>>the other 
>>guys to send upstream patches to developers to make sure their 
>>applications are ready for the new gcc-3.2 platform. (this 
>>will benefit 
>>all distros).
>>
>>-- 
>>Doug Goldstein
>>Developer (Laptops, WiFi, GCC-3.1)
>>Gentoo Linux                                
>>http://www.gentoo.org/~cardoe/
>>
>>    
>>
>
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
>
>  
>
Most of my patches are actually in the Gentoo source tree. When you 
emerge a package and you see a line that it's patching the source code 
right after unpacking the source... that's possibly one of the gcc-3.1 
patches. As far as where I send the patches to... I go to the 
maintainer's website and e-mail it to him/her and also explain all my 
changes. My patches aren't to specific Qt/GTK code because 99% of that 
code is fine. It's all C++ syntaxing and what not really. And if you 
wanna see lots of kernel hacks at patches by us Gentoo people... try 
mjc-sources. Make sure to pick your architecture with (3.1) at the end 
if you're using gcc-3.1.

-- 
Doug Goldstein
Developer (Laptops, WiFi, GCC-3.1)
Gentoo Linux                                http://www.gentoo.org/~cardoe/



_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev
[prev in list] [next in list] [prev in thread] [next in thread]