public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: alex@posixnap.net
To: gcc-gnats@gcc.gnu.org
Subject: other/10104: GCC 3.2.2 on Solaris 9 fails to install due to one missing symlink
Date: Sat, 15 Mar 2003 17:16:00 -0000	[thread overview]
Message-ID: <20030315171258.27387.qmail@sources.redhat.com> (raw)


>Number:         10104
>Category:       other
>Synopsis:       GCC 3.2.2 on Solaris 9 fails to install due to one missing symlink
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 15 17:16:02 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Alex Avriette
>Release:        3.2.2
>Organization:
>Environment:
Solaris 9 / 32-bit
>Description:
Reading specs from ./bin/../lib/gcc-lib/sparc-sun-solaris2.9/3.2.2/specs
Configured with: configure --prefix=/global/swdev/compilers/gcc-3.2.2-32bit --enable-languages=c
Thread model: posix
gcc version 3.2.2

SunOS detox 5.9 Generic_112233-03 sun4u sparc SUNW,Ultra-30

After running the configure and make, 'make install' fails in the gcc/mkinstalldirs script. It is looking for install-sh in "./../install-sh" -- but something is FUBAR, and it doesn't find it. Making a symlink into the <dist>/gcc directory to "../install-sh" fixes the problem, and it installs correctly.
>How-To-Repeat:
sh configure; make ; make install
>Fix:
Probably there is a more elegant fix than what I did, I'm sure it is just a matter of somebody biffing on the shell script with one too many "."s or somesuch.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-03-15 17:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030315171258.27387.qmail@sources.redhat.com \
    --to=alex@posixnap.net \
    --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).