public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/7237: HP/UX 10.20 compile problems, e.g, STAGE1_CFLAGS not overriden (fwd)
Date: Thu, 08 May 2003 23:46:00 -0000	[thread overview]
Message-ID: <20030508234601.21860.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/7237: HP/UX 10.20 compile problems, e.g, STAGE1_CFLAGS
 not overriden (fwd)
Date: Thu, 8 May 2003 18:39:25 -0500 (CDT)

 ---------- Forwarded message ----------
 Date: Thu, 8 May 2003 15:03:38 -0700 (PDT)
 From: Karri Balk <kbalk@pobox.com>
 To: bangerth@dealii.org
 Subject: Re: bootstrap/7237: HP/UX 10.20 compile problems, e.g,
      STAGE1_CFLAGS not overriden (fwd)
 
 Forwarded message:
 > From kbalk Thu May  8 14:40:22 2003
 > Subject: Re: bootstrap/7237: HP/UX 10.20 compile problems, e.g, STAGE1_CFLAGS not overriden
 > To: dhazeghi@yahoo.com (Dara Hazeghi)
 > Date: Thu, 8 May 2003 14:40:22 -0700 (PDT)
 > 
 > > 
 > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 > > trail&database=gcc&pr=7237
 > > 
 > > Hello,
 > > 
 > > can the submitter please verify that this bug still appears with a more  
 > > current version of gcc? We do have a report of a successful build of  
 > > gcc 3.2.2 on this platform, so _somebody_ seems to have succeeded.  
 > 
 > I no longer have access to a HP system to verify whether this is still 
 > a problem.  I'm sorry ...
 > 
 > I think my problem was related to limited disk space, as I was
 > making choices during the build process to reduce disk consumption.  
 > If this other person was able to do a standard, full, build, then 
 > they may not encounter the same problems.
 > 
 > Karri
 > 
 


                 reply	other threads:[~2003-05-08 23:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030508234601.21860.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.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).