> Nothing I can think of! ./bootstrap in the top level should make sure
> that a file install-sh is present in that top-level directory. Towards
> the end of the bootstrap, it copies install-sh from buildsupport to '.'
There were many lines
configure.ac: installing `./install-sh'
> and echos the cp, probably as the second-last line of its output. If
> the install-sh wasn't available to be copied for some reason, it should
> have produced an error message and an exit status.
>
> Do you have the file install-sh in that directory in fact?
Yes, in the cvs top-level directory.
> This is peculiar -- it hasn't happened to me before, and I think this
> is a pretty robust part of the bootstrap script. I'm stumped -- is
> there anything else that looks odd?
I have to admit to not being an avid reader of ./bootstrap output to
know if there's any abnormal messages.
There weren't any warning messages about versions of autoconf etc. being
missing. I know because I've tried ./bootstrap again, and those
appeared.
Malcolm
|