public inbox for
help / color / mirror / Atom feed
From: Phil Edwards <>
Subject: Re: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 30 Dec 2002 06:36:00 -0000	[thread overview]
Message-ID: <> (raw)

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

From: Phil Edwards <>
Subject: Re: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 30 Dec 2002 09:32:31 -0500

 On Mon, Dec 30, 2002 at 01:04:38PM -0000, wrote:
 > >Environment:
 > Solaris 9, Ultra 10
 > >Description:
 > When gcc/configure can't locate a BSD-comptible install program and chooses
 > to use install-sh, it places an incorrect path to it in ./intl/Makefile,
 > ./../install-sh.  There is no install-sh in intl's ./.. (gcc); it's in
 > ./../../, the grandparent of intl, gcc-3.2.1.  That causes the install rule
 > in gcc/Makefile to fail when it invokes the install rule in ./intl/Makefile.
 Did you see the installation instructions regarding
     1)  strongly recommending building in a seperate directory, and
     2)  special steps for Solaris systems?
 If you didn't, please try again after doing so, and let us know whether you
 still experience problems.
 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 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30  6:36 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:16 Phil Edwards
2002-12-30  7:06 Vic Abell
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).