This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: 1.3.20

> -----Original Message-----
> > To quote from the FAQ:
> >
> > "As of this writing, you need to install at least the cygwin source
> > package and the w32api source package.
> >
> > It is possible that the cygwin source package may require a newer
> > version of the w32api package since the release of the packages is not
> > always in lock step (another reason to just use CVS)."
> Otherwise why do you even bother giving people sources if you only intend
> them to use (the occasionally broken) CVS?

Excuse me for butting in on this thread, but I'm having trouble using the
cygwin CVS respository and since CVS seems to be the preferred method...

I'm trying to build a debug version of cygwin1.dll to help debug a problem
I'm having.  I'd like to retrieve the source files used to build cygwin
1.3.19-1 from CVS.  Following the instructions at
I tried to checkout this version  using:

	cvs checkout -r
cygwin-1-3-19-1 winsup

(BTW, the tag cygwin-1-3-19-1 isn't in the list of available tags in cvsweb
at, but it
is in CVS.)

I only got a portion of the source files (the files under
src/winsup/cygwin).  If I don't use the tag, I get all the sources, but I'm
getting files off the MAIN trunk that aren't tagged with cygwin-1-3-19-1.  I
don't think that's what I want since I'll be getting changes that have
occurred since the 1.3.19-1 release.  How do I get the versions of w32api,
newlib, etc. that were used to build 1.3.19-1 out of CVS?


P.S.  Jifl, welcome to the cygwin mailing list ;-).

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]