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: bootstrap/9238: make install: install-sh: not found
Date: Thu, 09 Jan 2003 22:56:00 -0000	[thread overview]
Message-ID: <20030109225602.30722.qmail@sources.redhat.com> (raw)

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

>From phil@jaj.com  Mon Jan 13 00:46:48 2003
From: Phil Edwards <phil@jaj.com>
To: "Mohler, Bruce" <Bruce_Mohler@intuit.com>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/9238: make install: install-sh: not found
Date: Thu, 9 Jan 2003 17:55:33 -0500

 On Thu, Jan 09, 2003 at 10:01:37AM -0800, Mohler, Bruce wrote:
 > Yes, in the top directory of the gcc 3.2 source tree, I:
 > 
 > mkdir gcc-3.0-sparc-32bit-obj
 > cd gcc-3.0-sparc-32bit-obj
 > ../configure --prefix=/usr/local \
 > 	--enable-languages=c,c++,java \
 > 	--disable-nls \
 > 	--host=sparc-sun-solaris2.8
 > make
 > ...
 
 That should work.  (Although your --prefix has always been the default,
 and the --host should be deduced automatically.)
 
 One suggestion:  try giving an absolute path to configure when you call
 it, e.g.,
 
     cd gcc-3.0-sparc-32bit-obj
     /wherever/you/unpacked/the/source/configure --enable-lan....
 
 and see whether the same error occurs during the build.
 
 -- 
 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:[~2003-01-09 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 22:56 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-15  7:46 ebotcazou
2003-02-22  7:08 neroden
2003-01-24 16:56 Bill C Riemers
2003-01-11 17:16 Mohler, Bruce
2003-01-09 23:26 Phil Edwards
2003-01-09 23:16 Mohler, Bruce
2003-01-09 18:06 Mohler, Bruce
2003-01-09  6:02 pme

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=20030109225602.30722.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).