Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Some Automake testsuite tests currently use
> ./configure ac_cv_prog_cc_stdc=no
>
> to force use of ansi2knr. I know the topic is becoming more and more
> obsolete,
It's not "more and more obsolete". It's obsolete, period. Nobody
uses K&R compile
On the FreeBSD and NetBSD testdrive hosts, remake4.test fails. It can
be "fixed" by adding some more sleep. For lack of better knowledge, I
assume non-synchronized clocks with the NFS server or so, given the
other oddities we've found with those systems.
What do you think? Does anybody have a b
* Ralf Wildenhues wrote on Sat, May 06, 2006 at 06:13:25PM CEST:
> Let's un-bitrot _AM_OUTPUT_DEPENDENCY_COMMANDS and make it nice and
> fast. We observe:
D'oh. Hitting y instead of P sucks. Please ignore this message; my
patch is not done yet.
Sorry for the noise,
Ralf
Let's un-bitrot _AM_OUTPUT_DEPENDENCY_COMMANDS and make it nice and
fast. We observe:
1) In the line,
| test -z "am__include" && continue
there's a `$' missing; but also, am__include may be `#' but not `'.
2) Some inconsistent quoting: for example, the argument to AS_MKDIR_P
has not been quoted
Some Automake testsuite tests currently use
./configure ac_cv_prog_cc_stdc=no
to force use of ansi2knr. I know the topic is becoming more and more
obsolete, but since there already is some backward compatibility code
to /set/ `ac_cv_prog_cc_stdc', it may also be prudent to honor a `no'
in this
1)
On alphaev7-dec-osf5.1b, pr401.test fails like this in the last part of
the test (subdir-objects, Test using LIBOBJS from parent directory, the
distcheck part from testSubDir/pr401-1.0/_build):
| configure: creating ./config.status
| config.status: creating Makefile
| config.status: executing d
