public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Joshua Daniel Franklin <joshuadfranklin@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin bughunt (FAQ alert?)
Date: Thu, 27 Jan 2005 01:56:00 -0000	[thread overview]
Message-ID: <cb51e2e050126143678bb7c36@mail.gmail.com> (raw)
In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB71097D8@dubexdc03.dubex.net>

On Wed, 26 Jan 2005 14:29:29 +0100, David Dindorp wrote:
> How about adding a line in the FAQ to the "how to build cygwin" (104)
> entry
> stating that the "configure ; make" mentioned does produce a Cygwin with
> all
> debugging symbols?
> 
> And the link in the FAQ is wrong:
> 
> "How can I debug cygwin" (entry 105) says:
> 
> "To build a debugging version of the Cygwin DLL,
>  you will need to follow the instructions at
>  http://cygwin.com/faq/faq_3.html#SEC102."
> 
> The above should point to entry 104, not 102.

Sorry, I'll fix this.

--
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/

  reply	other threads:[~2005-01-26 22:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26 15:19 David Dindorp
2005-01-27  1:56 ` Joshua Daniel Franklin [this message]
2005-01-27  4:51   ` Joshua Daniel Franklin
2005-01-27  6:38     ` Brian Dessent
  -- strict thread matches above, loose matches on Subject: below --
2005-01-26 16:35 David Dindorp
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 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
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
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=cb51e2e050126143678bb7c36@mail.gmail.com \
    --to=joshuadfranklin@gmail.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).