> > + eval ${SHELL} /pogo/users/stenn/src/ntp.001227/missing --run :
>
> I believe this can't be a problem in autoconf, since the `missing'
> script is maintained as part of automake and, indeed, the test to
> check whether it supports the `--run' switch relies upon `:'.
>
> Does missing work if, instead of:
>
> "$@" && exit 0
>
> the missing script did:
>
> prog=$1
> shift
> "$prog" ${1+"$@"} && exit 0
>
> ?
Still doesn't work, and should the second problem be forked into a thread
for autoconf while this one stays on automake?
Here's the current output:
configure: loading cache /dev/null
checking build system type... mips-dec-ultrix4.4
checking host system type... mips-dec-ultrix4.4
checking target system type... mips-dec-ultrix4.4
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/bin/sh: \272: not found
WARNING: `' is needed, and you do not seem to have it handy on your
system. You might have modified some files without having the
proper tools for further handling them. Check the `README' file,
it often tells you about the needed prerequirements for installing
this package. You may also peek at any GNU archive site, in case
some other package would contain this missing `' program.
configure: WARNING: `missing' script is too old or missing
...
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... # 1 "conftest.c"
# 1942 "configure"
# 1 "confdefs.h" 1
# 1943 "configure" 2
# 1 "/usr/local/mips-dec-ultrix4.4/include/assert.h" 1 3
...
H
