From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-developers@cygwin.com, Thomas Wolff <towo@towo.net>
Subject: Re: cygwin build
Date: Sun, 6 Aug 2023 19:53:02 +0100 [thread overview]
Message-ID: <16d27940-d011-c165-9557-9711672001c6@dronecode.org.uk> (raw)
In-Reply-To: <517f4a67-69ab-4234-bfec-b0ffb083fcd5@towo.net>
On 05/08/2023 19:18, Thomas Wolff wrote:
>
>
> Am 03.08.2023 um 15:12 schrieb Jon Turney:
>> On 03/08/2023 09:21, Thomas Wolff wrote:
>>> Am 02.08.2023 um 10:09 schrieb Corinna Vinschen:
>>>> On Aug 2 08:36, Thomas Wolff wrote:
>>>>>
>>>>> Am 01.08.2023 um 23:27 schrieb Corinna Vinschen:
>>>>>> On Aug 1 23:05, Thomas Wolff wrote:
>>>>>>> I took some of the latest cygwin snapshots (by the way, there are
>>>>>>> no newer
>>>>>>> ones on the snapshots page):
>>>>>> Snapshots are no longer produced. You should download the latest
>>>>>> test versions via setup.
>>>>> So what if I need an older version?
>>>> It's all documented:
>>>>
>>>> https://cygwin.com/git.html
>>>> https://cygwin.com/faq.html#faq.programming.building-cygwin
>>> Thanks. Actually package mingw zlib was missing (when I installed it,
>>> it got mistargeted to my parallel test installation).
>>> It now worked, kind of, with some build errors after producing the dll.
>>
>> Nobody can take any useful action about those "build errors" if you
>> keep them secret.
>>
> Sure, I just mentioned it and didn't post details as it wasn't essential
> for the discussed issue. Anyway, here are the final error message I
> often encounter:
>
> make[5]: Entering directory
> '/cygdrive/c/tmp/newlib-cygwin/build/x86_64-pc-cygwin/winsup/utils'
> CXXLD dumper.exe
> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../lib/libbfd.a(compress.o):
> in function `decompress_contents':
Ah, right.
This is a problem with the primitive time-travel technology you are using.
dumper relies on libbfd, which since binutils 2.40 relies on zstd.
bfd doesn't provide a .pc file, so the dependencies are explicitly
listed in our makefile.
You'll either needs to backport the commit [1] which adds zstd to the
link line to fix this, or also roll back binutils to the version which
was current when this built...
[1]
https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=1387ea9f984d5a7aa096a66b67d61dc2cc565d21;hp=588624da2b0a921c7e72d12d19c2ac3321de0326
next prev parent reply other threads:[~2023-08-06 18:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f0bfdf8-a557-0540-0367-6846406f941d@towo.net>
2023-08-01 21:05 ` Rare character glitch in pty? Thomas Wolff
2023-08-01 21:27 ` Corinna Vinschen
2023-08-02 6:36 ` cygwin build Thomas Wolff
2023-08-02 6:42 ` Takashi Yano
2023-08-02 8:09 ` Corinna Vinschen
2023-08-03 8:21 ` Thomas Wolff
2023-08-03 13:12 ` Jon Turney
2023-08-05 18:18 ` Thomas Wolff
2023-08-05 22:20 ` Takashi Yano
2023-08-06 6:51 ` Thomas Wolff
2023-08-06 18:53 ` Jon Turney [this message]
2023-08-07 6:11 ` Thomas Wolff
2023-08-07 8:25 ` Corinna Vinschen
2023-08-03 13:13 ` Jon Turney
2023-08-01 22:35 ` Rare character glitch in pty? Takashi Yano
2023-08-02 6:32 ` Thomas Wolff
2023-08-02 8:00 ` Takashi Yano
2023-08-02 13:16 ` Takashi Yano
2023-08-04 8:52 ` Takashi Yano
2023-08-04 11:33 ` Takashi Yano
2023-08-05 7:53 ` Thomas Wolff
2023-08-05 8:10 ` Takashi Yano
2023-08-07 8:28 ` Corinna Vinschen
2023-08-07 11:38 ` Takashi Yano
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=16d27940-d011-c165-9557-9711672001c6@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-developers@cygwin.com \
--cc=towo@towo.net \
/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).