This is the mail archive of the
mailing list for the Cygwin project.
Re: Compiling cygwin1.dll
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 03 Jun 2014 12:07:52 -0400
- Subject: Re: Compiling cygwin1.dll
- Authentication-results: sourceware.org; auth=none
- References: <CAALQ5rnJz9h-EHYR2UqoznOrhTVsqaqgX1KiWeD+fo1iKVt7sw at mail dot gmail dot com> <161164160 dot 20140603143233 at yandex dot ru> <CAALQ5rmK5pJEtJztUXs103YMmc1LE0O8DO7sb+1sBgFbsKt-Jg at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot com
On 06/03/2014 08:57 AM, Michael Wild wrote:
On Tue, Jun 3, 2014 at 12:32 PM, Andrey Repin wrote:
Greetings, Michael Wild!
In order to pinpoint an error I'm trying to compile cygwin1.dll from
source following the instructions here:
My question is: do you actually need to rebuild it, or you just need the debug
when building binutils, I trip over this error:
https://sourceware.org/ml/binutils/2014-02/msg00064.html. According to
"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.
I really need to build it, in order to pinpoint which commit breaks things.
OK but why are you building 'binutils' if you just want to build the Cygwin
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple