public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3250: gcc
Date: Fri, 18 Jan 2002 16:26:00 -0000	[thread overview]
Message-ID: <20020119002601.2387.qmail@sources.redhat.com> (raw)

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

From: Craig Rodrigues <rodrigc@mediaone.net>
To: law@redhat.com
Cc: jzago@ifaedi.insa-lyon.fr, gcc-gnats@gcc.gnu.org, rodrigc@gcc.gnu.org,
   gcc-bugs@gcc.gnu.org
Subject: Re: bootstrap/3250: gcc
Date: Fri, 18 Jan 2002 19:16:17 -0500

 On Fri, Jan 18, 2002 at 04:17:34PM -0700, law@redhat.com wrote:
 >  In message <20020118170524.A7988@mediaone.net>, Craig Rodrigues writes:
 >  > If gcc 2.95.xx is not supported on hpux11, does that mean that
 >  > bootstrapping gcc 3.0 with gcc 2.95 is also not supported?
 >  > If so, it would probably be a good idea to add this information 
 >  > to the host specific install notes.
 > Yes.  Can you do that for me?  
 
 OK, committed this:
 http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01307.html
 
 
 Now, PR 3250 reports the same error, but using
 gcc 2.95.3 on Solaris 2.5.1:
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&pr=3250&cmd=view
 
 steve@smc.vnet.net rejects my e-mail domain, so I can't get feedback. :(
 
 What should I do with this PR?
 -- 
 Craig Rodrigues        
 http://www.gis.net/~craigr    
 rodrigc@mediaone.net          


             reply	other threads:[~2002-01-19  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18 16:26 Craig Rodrigues [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-21  8:06 law
2002-01-18 15:26 law
2002-01-18 14:06 Craig Rodrigues
2002-01-18 13:46 Craig Rodrigues
2002-01-18 13:46 law
2002-01-18  9:06 jzago

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=20020119002601.2387.qmail@sources.redhat.com \
    --to=rodrigc@mediaone.net \
    --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).