public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: abe@purdue.edu
To: gcc-gnats@gcc.gnu.org
Subject: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 30 Dec 2002 05:06:00 -0000	[thread overview]
Message-ID: <20021230130438.25379.qmail@sources.redhat.com> (raw)


>Number:         9105
>Category:       other
>Synopsis:       gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 30 05:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Vic Abell
>Release:        3,2,1
>Organization:
>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.
>How-To-Repeat:
Attempt to install on a Solaris 9 system that has no BSD-compatible install program.
>Fix:
Hand edit gcc/inst/Makefile and correct the path to install-sh or copy gcc-3.2.1/install-sh to gcc-3.2.1/gcc.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-12-30 13:06 UTC|newest]

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

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=20021230130438.25379.qmail@sources.redhat.com \
    --to=abe@purdue.edu \
    --cc=gcc-gnats@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).