From: Michael Wild <mwild@bluewin.ch>
To: cygwin@cygwin.com
Subject: Compiling cygwin1.dll
Date: Tue, 03 Jun 2014 06:38:00 -0000 [thread overview]
Message-ID: <CAALQ5rnJz9h-EHYR2UqoznOrhTVsqaqgX1KiWeD+fo1iKVt7sw@mail.gmail.com> (raw)
Dear all
In order to pinpoint an error I'm trying to compile cygwin1.dll from
source following the instructions here:
https://cygwin.com/faq.html#faq.programming.building-cygwin. However,
when building binutils, I trip over this error:
https://sourceware.org/ml/binutils/2014-02/msg00064.html. According to
DJ (https://sourceware.org/ml/binutils/2014-02/msg00067.html),
"attempts to build the old binutils/gdb in CVS are going to be
doomed". Apparently the development of these packages is now tracked
in a separate git repo. So, my question is now, how do I get a working
build for the cygwin DLL? Do I have to replace binutils/gdb in the CVS
checkout with the git checkout?
How are the current snapshots built?
Thanks for any pointers in the right direction.
Michael
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2014-06-03 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 6:38 Michael Wild [this message]
2014-06-03 10:35 ` Andrey Repin
2014-06-03 12:58 ` Michael Wild
2014-06-03 16:08 ` Larry Hall (Cygwin)
2014-06-04 14:45 ` Michael Wild
2014-06-04 17:35 ` Andrey Repin
2014-06-04 19:19 ` Michael Wild
2014-06-04 20:05 ` Andrey Repin
2014-06-04 21:07 ` Christopher Faylor
2014-06-05 4:56 ` Michael Wild
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=CAALQ5rnJz9h-EHYR2UqoznOrhTVsqaqgX1KiWeD+fo1iKVt7sw@mail.gmail.com \
--to=mwild@bluewin.ch \
--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).