On Sat, Oct 12, 2002 at 01:09:05PM +0200, Jérôme Marant wrote: > On Fri, Oct 11, 2002 at 09:14:47PM +0200, Denis Barbier wrote: > > On Fri, Oct 11, 2002 at 03:13:20PM +0200, Maxence Guesdon wrote: > > > > > BTW, I'm surprised that autoconf is required since > > > > > a configure script is provided. > > > > > > > > Better ask Maxence on this issue then ... > > > > > > In fat, i give the .configure script like everyone does, but i give also > > > the configure.in script if someone needs to modify it (easier to modify > > > than the configure script). The Makefile also contains a target to > > > rebuild itself. > > > > > > Do you think I should remove this target ? and omve the configure.in > > > script in a subdir ? > > > > $ tar ztvf cameleon_1.1+cvs.20021009.orig.tar.gz | grep configure > > -rwxr-xr-x guesdon/cristal 43511 2002-08-26 11:42:25 > > cameleon-snapshot/configure > > -rw-r--r-- guesdon/cristal 6068 2002-08-26 11:42:26 > > cameleon-snapshot/configure.in > > [...] > > > > The configure script is older than configure.in ;) > > > > A workaround is to touch configure in debian/rules before running make, > > but there may be other timestamp problems. > > I think you found the origin of the problem. But I cannot how > the Makefile manages to call autoconf. The toplevel rules I invoke > do not lead to it.
Maybe an implicit configure: configure.in rule in make itself ? Friendly, Sven Luther
