Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dk@artimi.com>
To: "'Mark Helzer'" <Mark_Helzer@adp.com>, <gdb@sources.redhat.com>
Subject: RE: Install error on digital unix v4.0
Date: Thu, 09 Sep 2004 18:15:00 -0000	[thread overview]
Message-ID: <NUTMEGn20lbhsKd6QR70000128a@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <86F706952883A445B8B6D8ACF27C2B76E93717@nexus.plaza.ds.adp.com>

> -----Original Message-----
> From: gdb-owner On Behalf Of Mark Helzer
> Sent: 09 September 2004 18:26
> To: gdb
> Subject: Install error on digital unix v4.0
> 
> After compiling using gcc, I get the following error during "make
> install"

> sh: ./install-sh: not found


  These days, the very first thing that anybody should do when faced with a
new and confusing error message is STFW...

http://www.google.com/search?hl=en&ie=UTF-8&q=sh%3A+.%2Finstall-sh%3A+not+fo
und


... since 9 times out of 10, someone else will have had the same problem and
found a solution to it.

  In this case, the problem seems to be b0rkage in the top-level makefiles
that don't set the path to install-sh properly.  You can apparently specify
an override via an environment variable on the configure command line: and
since there is an install.sh in the gdb source distro, you might be able to
workaround the bug like this:

env INSTALL=/path/to/gdb/sources/gdb-6.2/install.sh configure <your config
options go here>

although another workaround that google search suggested would be just to cd
into the gdb subdir of your build dir and run the make install there.




    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


      parent reply	other threads:[~2004-09-09 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 17:25 Mark Helzer
2004-09-09 18:11 ` Michael Chastain
2004-09-09 18:15 ` Dave Korn [this message]

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=NUTMEGn20lbhsKd6QR70000128a@NUTMEG.CAM.ARTIMI.COM \
    --to=dk@artimi.com \
    --cc=Mark_Helzer@adp.com \
    --cc=gdb@sources.redhat.com \
    /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