Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Jim Ingham <jingham@apple.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>, gdb@sources.redhat.com
Subject: Re: Apple and gcc 2?
Date: Mon, 22 Sep 2003 20:36:00 -0000	[thread overview]
Message-ID: <3F6F5D5F.5090105@apple.com> (raw)
In-Reply-To: <712014EF-EAE4-11D7-A429-00039379E320@apple.com>

Jim Ingham wrote:

> Michael,
>
> On Sep 19, 2003, at 1:54 PM, Michael Elizabeth Chastain wrote:
>
>> (Obviously where I'm going with this is: figuring out when gdb
>> can drop support for gcc 2).
>
>
> I can't really speak to this.  I don't really know if/when we are 
> going to drop support for compiling kext's with 2.95.

Apple's hacked GCC 2.95 is needed to build device drivers that will run on
Mac OS X 10.1 and 10.0 systems.  While probably there are few 10.0
systems out there, there may be several million 10.1 systems, and hardware
makers that want to sell to those users will want a GCC 2 compiler. I can't
predict when the demand will go away, but presumably at some point the
devices' boxes will all say "10.2 or higher only" because the extra
sales to 10.1 users won't pay for the necessary testing.

Stan



  reply	other threads:[~2003-09-22 20:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 20:54 Michael Elizabeth Chastain
2003-09-19 21:01 ` Jim Ingham
2003-09-22 20:36   ` Stan Shebs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-22 22:05 Michael Elizabeth Chastain
2003-09-22 21:18 Michael Elizabeth Chastain
2003-09-22 21:27 ` Mark Kettenis
2003-09-22 21:31 ` Andrew Cagney
2003-09-19 22:06 Michael Elizabeth Chastain
2003-09-19 18:16 Michael Elizabeth Chastain
2003-09-19 18:30 ` Jim Ingham

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=3F6F5D5F.5090105@apple.com \
    --to=shebs@apple.com \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.com \
    --cc=mec@shout.net \
    /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