From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Can't compile mintty-3.5.0
Date: Mon, 26 Apr 2021 14:14:14 +0200 [thread overview]
Message-ID: <3b999c0b-6731-01d9-5908-37b6410dd3e1@towo.net> (raw)
In-Reply-To: <af93be95-411c-bf26-678e-0383733e8cbb@cs.umass.edu>
Am 26.04.2021 um 14:06 schrieb Eliot Moss:
> On 4/26/2021 8:00 AM, Lemures Lemniscati via Cygwin wrote:
>> Hi!
>>
>> I tried to compile mintty-3.5.0,
>> but failed with the message:
>>
>> windres -c 65001 --preprocessor 'gcc -E -xc -DRC_INVOKED -MMD -MP
>> -DTARGET=x86_64-pc-cygwin -DNDEBUG' res.rc ../bin/cygwin64/res.o
>> /bin/sh: gcc -E -xc -DRC_INVOKED -MMD -MP -DTARGET=x86_64-pc-cygwin
>> -DNDEBUG: command not found
>> windres: preprocessing failed.
This is due to a bug in windres. The binutils 2.36 version is broken,
see https://sourceware.org/bugzilla/show_bug.cgi?id=27594
A workaround is available but I'd prefer to let them fix their bug.
For now, please downgrade binutils to 2.35 and maybe make a copy of its
windres tool into your path.
Thomas
>>
>>
>> ====
>> How to reproduce
>>
>> With source from https://github.com/mintty/mintty at tag: 3.5.0,
>> running
>>
>> make
>>
>> failed at the point above.
>> .
>> With mintty-3.5.0-1.cygport,
>> running
>>
>> cygport mintty-3.5.0-1.cygport all
>>
>> failed at the same point.
>>
>>
>> ====
>> I've installed these packages as described in a file 'INSTALL'.
>> What is still necessary for successful build ?
>>
>> ----
>> $ uname -svrmo; cygcheck -c gcc-core make
>> CYGWIN_NT-10.0 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin
>> Cygwin Package Information
>> Package Version Status
>> gcc-core 10.2.0-1 OK
>> make 4.3-1 OK
>> ----
>
> windres should be in the binutils package.
>
> EM
>
next prev parent reply other threads:[~2021-04-26 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 12:00 Lemures Lemniscati
2021-04-26 12:06 ` Eliot Moss
2021-04-26 12:14 ` Thomas Wolff [this message]
2021-04-29 4:46 ` Brian Inglis
2021-04-29 16:46 ` Achim Gratz
2021-04-26 13:35 ` Lemures Lemniscati
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=3b999c0b-6731-01d9-5908-37b6410dd3e1@towo.net \
--to=towo@towo.net \
--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).