From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Can't compile mintty-3.5.0
Date: Wed, 28 Apr 2021 22:46:07 -0600 [thread overview]
Message-ID: <d6ae488e-d229-119f-c6a6-250330c1d00b@SystematicSw.ab.ca> (raw)
In-Reply-To: <3b999c0b-6731-01d9-5908-37b6410dd3e1@towo.net>
On 2021-04-26 06:14, Thomas Wolff wrote:
> Am 26.04.2021 um 14:06 schrieb Eliot Moss:
>> On 4/26/2021 8:00 AM, Lemures Lemniscati via Cygwin wrote:
>>> 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.
>> windres should be in the binutils package.
> 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.
Suggest Cygwin binutils windres be updated to revert the patch like Msys2:
https://github.com/msys2/MSYS2-packages/pull/2384
as nothing appears to be happening with the issue in binutils; or else the
downstreams need to use options as implemented rather than as per examples.
I'd expect a fix to the doc example rather than the code, as the developers may
be going in a new direction, possibly to keep up with Windows updates.
It also appears that the quot() function should have been used rather than
asprintf, as it takes account of build environment quoting rules, although it
would be better if it could find out about and take account of the *runtime*
shell environment quoting rules.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-04-29 4:46 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
2021-04-29 4:46 ` Brian Inglis [this message]
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=d6ae488e-d229-119f-c6a6-250330c1d00b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).