public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Vic Abell" <abe@purdue.edu>
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: Wed, 21 May 2003 11:28:00 -0000	[thread overview]
Message-ID: <20030521112601.21132.qmail@sources.redhat.com> (raw)

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

From: "Vic Abell" <abe@purdue.edu>
To: "Eric Botcazou" <ebotcazou@libertysurf.fr>
Cc: "'Christian Ehrhardt'" <ehrhardt@mathematik.uni-ulm.de>,
   <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: RE: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Wed, 21 May 2003 06:22:56 -0500

 Erc,
 
 You write:
 >
 > I wrote:
 > >
 > > Yes.  No difference.  The INSTALL string in gcc/intl/Makefile
 > > is wrong if "/path/to/sources/configure" is relative; correct,
 > > if it is absolute.
 > 
 > So everything works fine unless you build in the src directory, 
 > doesn't it?
 
 No.  It makes no difference if the configure step is
 run in-source or ex-source.   If done ex-source with
 a relative path, the gcc/intl/Makefile's INSTALL string
 is missing one "../" component. 


             reply	other threads:[~2003-05-21 11:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 11:28 Vic Abell [this message]
  -- strict thread matches above, loose matches on Subject: below --
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:16 Phil Edwards
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=20030521112601.21132.qmail@sources.redhat.com \
    --to=abe@purdue.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).