Yoshiaki> It seems that 'configure.in' in the CVS repository was Yoshiaki> updated, but 'configure' is not yet... SJT> I thought that the policy was that CVS did not have configure, only SJT> configure.in. Maybe that's only wishful thinking on my part. :-/ If configure was not in CVS, you wouldn't be able to do cvs checkout; configure; make SJT> I'll fix this right away. SJT> Is there a problem with CVS users and autoconf? I thought that the SJT> big problem was native NT builds, and they don't use configure at all. This is a big controversial thing. Generating all files requires perl and autoconf, and because CVS timestamps can't be trusted, the generated files must be regenerated for every build. cvs update; rebuild-all-generated-files; configure; make My own personal build scripts try to guarantee that my own files are up to date - exporting this functionality for everyone is a Project. I try to guarantee that all generated files are up-to-date in CVS at the time of a release (this is mostly automated) - that's how `depend' got updated for Millennium. Of course, developers are still supposed to commit generated files when making changes, but this is not critical for most generated files like `depend'. Martin