This is the mail archive of the
mailing list for the Cygwin project.
Re: Setup cvs HEAD build problems
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Max Bowsher <maxb at ukf dot net>
- Cc: cygwin-apps at cygwin dot com
- Date: Wed, 12 Mar 2003 15:11:19 -0500 (EST)
- Subject: Re: Setup cvs HEAD build problems
- Reply-to: cygwin-apps at cygwin dot com
On Wed, 12 Mar 2003, Max Bowsher wrote:
> Robert Collins wrote:
> > On Tue, 2003-03-11 at 03:37, Max Bowsher wrote:
> >>> Ok, well I'm going to practice delegation here: Max - when you look
> >>> at zlib, can you ensure that the timestamps on zlib's autotool
> >>> files are correctly ordered?
> >> Delegation accepted, but I think it's potentially more complicated
> >> than that. I'll dig up some docs on the subject.
> > Nyah, its not complicated:
> > the autoconf and automake files are timestamped. If you run make dist
> > in an automake project in the zlib directory, you'll get a 'pristine'
> > tarball with monotonically increasing dates across the source and
> > generated files. Similarly for autoconf without automake, you need to
> > produce (from memory)
> > configure.in <= acinclude.m4 < aclocal.m4 < autoconf.h.in < configure.
> > That needs to be reflected in CVS.
> I've remembered the complication I mentioned: cvs checkout recreates
> timestamps from the repository, but cvs update does not. However, this won't
> bother us, since we hardly ever update the zlib/bz2lib/rsync subdirs.
> I'll verify the order you quote above, and make appropriate changes to CVS.
I think this might have been the source of my original problem -- I did an
"update" instead of a "checkout"... Does this merit a note on the setup
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!