Re: Install error on digital unix v4.0

[Michael Chastain <mec dot gnu at mindspring dot com>]

"Mark Helzer" <Mark_Helzer@adp.com> wrote:
> if test ! -f standards.info; then cd .; fi;  if test -f standards.info;
> then  fo
> r i in standards.info*; do  ./install-sh -c -m 644 $i
> /usr/local/info/$i;  done;
>   fi
> sh: ./install-sh: not found
> *** Exit 1
> Stop.
> *** Exit 1
> Stop.

On my system, native i686-pc-linux-gnu with red hat 8.0,
this part of install.log looks like:

  if test ! -f standards.info; then cd /berman/migchain/source/gdb-6.2.1/etc; fi; \
  if test -f standards.info; then \
    for i in standards.info*; do \
      /usr/bin/install -c -m 644 $i /berman/migchain/install/target/native/gdb-6.2.1/info/$i; \
    done; \
  fi

Look at this part of the beginning of my configure.log:

  creating cache ./config.cache
  checking host system type... i686-pc-linux-gnu
  checking target system type... i686-pc-linux-gnu
  checking build system type... i686-pc-linux-gnu
  checking for a BSD compatible install... /usr/bin/install -c

And here is another configure.log excerpt from gdb 6.2
on native hppa2.0w-hp-hpux11.00:

  creating cache ./config.cache
  checking host system type... hppa2.0w-hp-hpux11.00
  checking target system type... hppa2.0w-hp-hpux11.00
  checking build system type... hppa2.0w-hp-hpux11.00
  checking for a BSD compatible install... /home/mec/source/gdb-6.2/install-sh -c

Can you check the beginning of your configure.log?  I bet that it has a
value for "BSD compatible install" with has a relative path in it,
like "./install-sh".  And then later, at "make install" time,
that non-absolute path does not work.

Two things to try:

(1) Use a separate build directory from the source directory.
    And use an absolute path for running the configure script.

    mkdir /foo/bar/build
    cd /foo/bar/build
    /foo/bar/gdb-6.2/configure --prefix=/whatever
    make
    make install

(2) Or, try setting the INSTALL environment variable to an absolute path:

    INSTALL=/foo/bar/gdb-6.2/install-sh
    export INSTALL

With either method, check the "BSD compatible install" line at the top 
of configure.log (your log from the "configure" command) and make sure
that it's got an absolute path.

I've built gdb 6.0 on native alphaev56-dec-osf4.0g using method (1)
using gnu make 3.79.1, gcc 3.3.4, and the vendor-supplied assembler and
linker.  But gdb 6.1, gdb 6.1.1, and gdb 6.2 don't build for me because
of PR gdb/1626, the ncurses library problem.

Hope this helps,

Michael Chastain