From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin bughunt (FAQ alert?)
Date: Fri, 21 Jan 2005 19:26:00 -0000 [thread overview]
Message-ID: <20050121190233.GD20866@trixie.casa.cgf.cx> (raw)
In-Reply-To: <Pine.GSO.4.61.0501211146420.18105@slinky.cs.nyu.edu>
On Fri, Jan 21, 2005 at 11:53:25AM -0500, Igor Pechtchanski wrote:
>Also agreed. But the source provided in the cygwin source package is
>worthless for debugging, since one can't build Cygwin from that source.
>If debugger symbols were available, that source would actually be
>useful. :-)
Huh?
tar xjf cygwin-1.5.12-1-src.tar.bz2
cd cygwin-1.5.12-1
mkdir build
cd build
(../configure; make) >& make.out
This builds a cygwin DLL. Just tried it.
Since all of your arguments were presupposing something to do with CVS,
I assume that this addresses your concerns. You don't need CVS and I
did not say that you had to use CVS.
It does make sense to check CVS or a snapshot to see if your problem is
fixed before you go to any effort trying to debug a problem, however.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2005-01-21 19:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 12:04 Hughes, Bill
2005-01-21 12:56 ` Corinna Vinschen
2005-01-21 16:57 ` Christopher Faylor
2005-01-21 17:00 ` Igor Pechtchanski
2005-01-21 18:21 ` Corinna Vinschen
2005-01-21 19:26 ` Christopher Faylor [this message]
2005-01-21 19:42 ` Igor Pechtchanski
2005-01-21 21:54 ` Christopher Faylor
2005-01-21 19:47 ` Pierre A. Humblet
2005-01-21 22:00 ` Christopher Faylor
2005-01-21 23:11 ` Pierre A. Humblet
2005-01-22 4:26 ` Christopher Faylor
2005-01-22 21:00 ` Joshua Daniel Franklin
2005-01-22 22:23 ` Christopher Faylor
2005-01-22 23:44 ` Joshua Daniel Franklin
2005-01-23 1:00 ` Christopher Faylor
2005-01-24 6:52 ` Joshua Daniel Franklin
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 16:35 David Dindorp
2005-01-26 15:19 David Dindorp
2005-01-27 1:56 ` Joshua Daniel Franklin
2005-01-27 4:51 ` Joshua Daniel Franklin
2005-01-27 6:38 ` Brian Dessent
2005-01-25 20:10 David Dindorp
2005-01-25 21:59 ` Igor Pechtchanski
2005-01-25 22:54 ` Christopher Faylor
2005-01-21 18:49 David Dindorp
2005-01-22 12:18 ` Christopher Faylor
2005-01-21 14:59 Hughes, Bill
2005-01-21 0:39 David Dindorp
2005-01-21 1:01 ` Christopher Faylor
2005-01-21 8:30 ` Joshua Daniel Franklin
2005-01-20 20:05 cygwin bughunt David Dindorp
2005-01-20 20:47 ` cygwin bughunt (FAQ alert?) Christopher Faylor
2005-01-20 21:21 ` Joshua Daniel Franklin
2005-01-20 21:35 ` Christopher Faylor
2005-01-20 21:38 ` Igor Pechtchanski
2005-01-20 21:47 ` Christopher Faylor
2005-01-20 22:35 ` Pierre A. Humblet
2005-01-21 11:57 ` Corinna Vinschen
2005-01-21 15:59 ` Pierre A. Humblet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050121190233.GD20866@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).