On Tue, Oct 24, 2006 at 06:04:30PM +0200, Stepan Kasal wrote:
> I think I have found the bug now.
...
> The fix is obvious: `autom4te' should always create the output file,
> if --force was given. Patch attached.
> I committed it to the Autoconf CVS.
>
> Greg, if you are willing to test the fi
On Tue, Oct 24, 2006 at 02:29:01PM +0200, Ralf Wildenhues wrote:
> Since we fixed autoconf/lib/autom4te.cfg in Autoconf 2.60, now when we
> call $ACLOCAL, the traces that were created by the $AUTOCONF before are
> sufficient; and since they appear with the same time stamp as all known
> input files
On Tue, Oct 24, 2006 at 12:30:45PM +0200, Stepan Kasal wrote:
> I stared at the code for a while but I wasn't find other potential
> cause of the problem. I would like to understand the cause of the
> problem, and thus I'd be grateful if you could perform some experiments
> to help us to find it.
On Thu, Oct 19, 2006 at 08:51:11AM +0200, Ralf Wildenhues wrote:
> Out of curiosity: how fast is this machine, how many and what kind of
> CPUs does it have?
Reasonably fast. 1 x AMD Athlon64 X2 4200+ (dual core).
> Could you please show the time stamps when the failure happens. Like
> this (in
Hi
I'm testing automake-1.10 on i686-pc-linux-gnu and seeing an intermittent
failure of acloca20.test. It fails for me roughly 1 in 4 attempts, but then
other times it will pass 10 times in a row. Here's the verbose output when
it fails:
$ make check TESTS=acloca20.test VERBOSE=x
make defs aclo
On Mon, Mar 14, 2005 at 11:39:28PM +0100, Alexandre Duret-Lutz wrote:
> On Tue, Mar 15, 2005 at 09:12:43AM +1100, Greg Schafer wrote:
> >
> > The issue is still present
>
> Could you show it to us?
Sure. The output is attached.
Regards
Greg
$ make -C gettext-tools/mis
On Fri, Feb 25, 2005 at 01:39:50PM +0100, Bruno Haible wrote:
> Greg Schafer wrote:
> > gettext-0.14.2 seems to work well in general, but there is a problem on
> > parallel builds in the `gettext-tools/misc' dir. You should be able to
> > reproduce the problem by ru
