public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Mattsson" <michael@kyrana.com>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] GCC 3.1/3.2
Date: Sun, 28 Jul 2002 14:27:07 -0400	[thread overview]
Message-ID: <004801c23664$61af67b0$0a01a8c0@neptune> (raw)
In-Reply-To: <3D43F0B5.9030203@gentoo.org>


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/
> 




  parent reply	other threads:[~2002-07-28 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28  5:07 [gentoo-dev] GCC 3.1/3.2 Matthew J. Turk
2002-07-28 10:44 ` Bart Verwilst
2002-07-28 13:25   ` Doug Goldstein
2002-07-28 17:26     ` Terje Kvernes
2002-07-28 17:44     ` Matthew J. Turk
2002-07-28 18:27     ` Michael Mattsson [this message]
2002-07-28 22:16       ` Doug Goldstein
  -- strict thread matches above, loose matches on Subject: below --
2002-07-28 22:01 Thomas Beaudry
2002-07-29  7:14 Michael Mattsson
2002-07-29 10:09 ` Matthew Kennedy
2002-07-29  7:28 Thomas Beaudry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004801c23664$61af67b0$0a01a8c0@neptune' \
    --to=michael@kyrana.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox