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: Thu, 3 Aug 2023 10:21:23 +0200	[thread overview]
Message-ID: <550b3262-e0f1-94c1-6526-3f3ef9d29d21@towo.net> (raw)
In-Reply-To: <ZMoPSin4OoE9hCpI@calimero.vinschen.de>



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.
However, after I checked out an older git commit, rebuild fails again:
make[4]: Entering directory 
'/cygdrive/c/tmp/newlib-cygwin/build/x86_64-pc-cygwin/newlib/libc'
make[4]: *** No rule to make target 'all'.  Stop.
So I'm not getting another dll after changing the git reference.

>
> Creating snapshots was a really outdated method.  It relied on on a
> non-standard, third-party script system, which started to fray at the
> edges.  So we switched to an automated build system which creates test
> releases on every Cygwin-related change to the git repository instead.
> When we did that I think I even made a matching announcement on the
> mailing list.
Setup offers 3.5.0 versions but not older ones. So a working build 
process would be essential for certain bug analysis.
Thomas

>
>
> Corinna


  reply	other threads:[~2023-08-03  8:21 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 [this message]
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
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=550b3262-e0f1-94c1-6526-3f3ef9d29d21@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).