The failure to start seems to have been fixed (or at least, fixed) by the
0.9.21-1.2+b1 binNMU on amd64.
Yes, the problem was that the touch config.h.in didn't have any effect
probably because it was built in a very fast buildd and ext3 only has a
1 second resolution.
It's a timing/resolution
On Wed, 07 Apr 2010 at 11:54:23 +0200, Torsten Marek wrote:
I've checked some other architecture's buildd logs, they look exactly
like the local one.
The failure to start seems to have been fixed (or at least, fixed) by the
0.9.21-1.2+b1 binNMU on amd64.
Simon
--
To UNSUBSCRIBE, email
Hi,
something is strange in there. If you check the build log, you'll see
that configure is run twice, then config.h.in is regenerated using
autoheader, but config.h is build via config.status only after make
all-recursive is executed.
In a local build, config.h is created immediately after
3 matches
Mail list logo
