On Tue, 12 Apr 2005, Dave Korn wrote:
----Original Message----
From: Ray Holme
Sent: 12 April 2005 13:42
the install-sh is always referenced in the parent directory.
(../install-sh)
so for all the first level directories in the install directory - one copy
at the top will do.
now for sub-sub directories - you must copy (or link) one into the parent
sub-directory.
I don't think there are any three level install directories (but don't
quote me).
Wouldn't it be an awful lot easier to just
A) apply the previously-mentioned fix to toplevel?
If I knew where it was mentioned, probably.
B) use a full path to configure, since this only crops up when using a
relative path to the configure script?
This seems to be what happened in practice, but my :
cp gcc-3.4.3/install-sh gcc-3.4.3/boehm-gc
cp gcc-3.4.3/install-sh gcc-3.4.3/config
cp gcc-3.4.3/install-sh gcc-3.4.3/contrib
cp gcc-3.4.3/install-sh gcc-3.4.3/fastjar
cp gcc-3.4.3/install-sh gcc-3.4.3/gcc
cp gcc-3.4.3/install-sh gcc-3.4.3/include
cp gcc-3.4.3/install-sh gcc-3.4.3/intl
cp gcc-3.4.3/install-sh gcc-3.4.3/libf2c
cp gcc-3.4.3/install-sh gcc-3.4.3/libffi
cp gcc-3.4.3/install-sh gcc-3.4.3/libiberty
cp gcc-3.4.3/install-sh gcc-3.4.3/libjava
cp gcc-3.4.3/install-sh gcc-3.4.3/libobjc
cp gcc-3.4.3/install-sh gcc-3.4.3/libstdc++-v3
cp gcc-3.4.3/install-sh gcc-3.4.3/maintainer-scripts
cp gcc-3.4.3/install-sh gcc-3.4.3/zlib
didn't seem to break anything, and the install completed
successfully. Anyway, hopefully any problem will vanish when
3.4.4 comes out.
cheers,
DaveK
Thank you,
Hugh
