public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/7604: GCC3.1 does not compile on openstep4.2
Date: Thu, 15 Aug 2002 14:16:00 -0000	[thread overview]
Message-ID: <20020815200601.29463.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/7604; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: Opensource@chollian.net
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: other/7604: GCC3.1 does not compile on openstep4.2
Date: Thu, 15 Aug 2002 15:46:57 -0400

 Do you read this part:
 
 On Thursday, August 15, 2002, at 02:55 , Opensource@chollian.net wrote:
 
 >
 > *** Configuration i386-next-openstep4 is obsolete.
 > *** Specify --enable-obsolete to build it anyway.
 > *** Support will be REMOVED in the next major release of GCC,
 > *** unless a maintainer comes forward.
 
 Thanks,
 Andrew Pinski
 


             reply	other threads:[~2002-08-15 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 14:16 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-10  9:17 ehrhardt
2002-08-15 12:56 Opensource

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=20020815200601.29463.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).