From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@Shaw.ca>,
Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: Cygwin build utils dumper fails - new prereqs required?
Date: Fri, 17 Feb 2023 13:14:36 +0000 [thread overview]
Message-ID: <cf7530d5-2b99-b6b1-1b14-42c2707ac10c@dronecode.org.uk> (raw)
In-Reply-To: <545a5149-0470-6541-9a27-5cdb74f646c6@Shaw.ca>
On 16/02/2023 23:02, Brian Inglis wrote:
> Hi folks,
>
> Building Cygwin from latest repo testing some unrelated doc patches and
> updated Unicode tables.
> Cygwin utils fails to build dumper.
> References to elf and binutils debuginfo, and undefined references to
> sframe_de-/encode ZSTD_de-/compress/_isError in attached log - config
> and normal processing suppressed and paths sanitized!
> Are new prereqs required to be installed to satisfy, or something
> changed to suppress these references?
Yes, to build dumper with libbfd from binutils 2.40, you need
libzstd-devel and
https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=1387ea9f984d5a7aa096a66b67d61dc2cc565d21
next prev parent reply other threads:[~2023-02-17 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:02 Brian Inglis
2023-02-17 13:14 ` Jon Turney [this message]
2023-02-17 17:35 ` Brian Inglis
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=cf7530d5-2b99-b6b1-1b14-42c2707ac10c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@Shaw.ca \
--cc=cygwin-patches@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).