public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8124: GCC 3.2 make install error
Date: Wed, 14 May 2003 09:36:00 -0000	[thread overview]
Message-ID: <20030514093603.19277.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: eric.thomas2@voila.fr, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/8124: GCC 3.2 make install error
Date: Wed, 14 May 2003 02:33:23 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=8124
 
 Hello,
 
 this looks like one of those bugs that comes from building in the gcc  
 source directory (objdir==srcdir). I believe this problem is fixed in  
 gcc 3.3. Would it be possible for the submitter to check whether this  
 is in fact the case? Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-14  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  9:36 Dara Hazeghi [this message]
2003-05-14 10:53 giovannibajo

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=20030514093603.19277.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --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).