public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-developers@cygwin.com
Subject: Re: cygwin build
Date: Sun, 6 Aug 2023 08:51:56 +0200	[thread overview]
Message-ID: <2a4503f5-fcb8-ceb8-afcf-4540934b02b4@towo.net> (raw)
In-Reply-To: <20230806072058.004a6000252f5e9fcb4aa2c7@nifty.ne.jp>


Am 06.08.2023 um 00:20 schrieb Takashi Yano:
> On Sat, 5 Aug 2023 20:18:43 +0200
> 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':
>> /usr/src/debug/binutils-2.41-1/bfd/compress.c:514:(.text+0x20d):
>> undefined reference to `ZSTD_decompress'
>> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
>> /usr/src/debug/binutils-2.41-1/bfd/compress.c:516:(.text+0x215):
>> undefined reference to `ZSTD_isError'
>> /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 `bfd_compress_section_contents':
>> /usr/src/debug/binutils-2.41-1/bfd/compress.c:653:(.text+0x11e4):
>> undefined reference to `ZSTD_compress'
>> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
>> /usr/src/debug/binutils-2.41-1/bfd/compress.c:658:(.text+0x11f1):
>> undefined reference to `ZSTD_isError'
>> collect2: error: ld returned 1 exit status
>> make[5]: *** [Makefile:603: dumper.exe] Error 1
>> make[5]: Leaving directory
>> '/cygdrive/c/tmp/newlib-cygwin/build/x86_64-pc-cygwin/winsup/utils'
>> make[4]: *** [Makefile:872: all-recursive] Error 1
>> make[4]: Leaving directory
>> '/cygdrive/c/tmp/newlib-cygwin/build/x86_64-pc-cygwin/winsup/utils'
>> make[3]: *** [Makefile:512: all] Error 2
>> make[3]: Leaving directory
>> '/cygdrive/c/tmp/newlib-cygwin/build/x86_64-pc-cygwin/winsup/utils'
>> make[2]: *** [Makefile:395: all-recursive] Error 1
>> make[2]: Leaving directory
>> '/cygdrive/c/tmp/newlib-cygwin/build/x86_64-pc-cygwin/winsup'
>> make[1]: *** [Makefile:9464: all-target-winsup] Error 2
>> make[1]: Leaving directory '/cygdrive/c/tmp/newlib-cygwin/build'
>> make: *** [Makefile:883: all] Error 2
> That happened to me before.
>
> Install libzstd-devel.
> Remove
> ./etc/config.cache
> ./x86_64-pc-cygwin/newlib/config.cache
> ./x86_64-pc-cygwin/winsup/config.cache
> Re-run ./configure && make.
Yes, thanks, that dependency is missing in the FAQ.

  reply	other threads:[~2023-08-06  6:51 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 [this message]
2023-08-06 18:53               ` Jon Turney
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=2a4503f5-fcb8-ceb8-afcf-4540934b02b4@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-developers@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).