On Monday, June 20, 2011 12:50:02 Jim Edwards wrote: > As I understand it, I should be able to bootstrap on a single system, check > in the resulting configure and Makefile.in files then on other systems > I should only need to run configure. But this doesn't seem to be working, > I get something like ... > > cd . && /bin/sh /ptmp/jedwards/glimmer-cism/gc2_trunk/missing --run > aclocal-1.10 > cd . && /bin/sh /ptmp/jedwards/glimmer-cism/gc2_trunk/missing --run > automake-1.10 --foreign > > > What do I need to do to prevent this? checking in generated autotool files (i.e. configure and Makefile.in) is generally discouraged. you're hitting a timestamp issue because when people checkout/update the sources, the timestamps on the files dont match and autotools regenerates itself automatically. you have a few choices: - dont check in these files and do as Eric said - dont distribute this way ... use `make dist` and distribute the tarball as is the standard in the world - have everyone run `find . -exec touch -r configure {} +` before running `./configure` ... but this wouldnt really fix use cases of `svn up && make`, so you're better off not ... -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf