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
symbols?
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.
Dear Andrey,
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
DLL?
--
Larry
_____________________________________________________________________
A: Yes.
> 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
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
