public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 30 Dec 2002 07:16:00 -0000	[thread overview]
Message-ID: <20021230151601.24607.qmail@sources.redhat.com> (raw)

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

From: Phil Edwards <phil@jaj.com>
To: Vic Abell <abe@purdue.edu>
Cc: gcc-gnats@gcc.gnu.org, vicabell <abe@vic.cc.purdue.edu>
Subject: Re: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 30 Dec 2002 10:07:15 -0500

 On Mon, Dec 30, 2002 at 10:02:26AM -0500, Vic Abell wrote:
 > 
 > I don't find anything I should change in the way I built
 > gcc-3.2.1, but I may be missing some references.  Could you please
 > identify those?
 
 Start at http://gcc.gnu.org/install/ and go from there.
 
 There have been bugs with in-source-dir configuration in the past, but if
 you've not done that then all should be well... hmm.
 
 
 Phil
 
 -- 
 I would therefore like to posit that computing's central challenge, viz. "How
 not to make a mess of it," has /not/ been met.
                                                  - Edsger Dijkstra, 1930-2002


             reply	other threads:[~2002-12-30 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30  7:16 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-21 11:28 Vic Abell
2003-05-21 10:48 Eric Botcazou
2003-05-21 10:19 Vic Abell
2003-05-21  9:36 Christian Ehrhardt
2003-05-19 13:56 Vic Abell
2003-05-15  4:36 bangerth
2003-05-14 22:06 Dara Hazeghi
2003-05-14 19:46 Dara Hazeghi
2002-12-30  7:06 Vic Abell
2002-12-30  6:36 Phil Edwards
2002-12-30  5:06 abe

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=20021230151601.24607.qmail@sources.redhat.com \
    --to=phil@jaj.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).