zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: PATCH: separate watch/log functionality out into a module
Date: Thu, 11 Nov 2021 18:08:30 +0100	[thread overview]
Message-ID: <93977-1636650510.897657@B71Q.U4fb.k4DR> (raw)
In-Reply-To: <F80A0CEA-3C20-491E-B15B-1ECC544ABE8F@kba.biglobe.ne.jp>

Jun T wrote:
>
> With this patch (either with or without the one in worker/49544⁩),
> build fails on Cygwin as follows:

Thanks for catching this.

> A simple workaround is to set the .gsu in the setup_() function.
> This takes virtually no time to execute and I think we don't need to use
> #ifdef __CYGWIN__.

That sounds reasonable to me.

That is assuming I didn't get something wrong when tagging visibility
on the structs and their members. I wouldn't have complete faith in
the build system to adapt to those changes so, if you didn't already,
start with an absolutely clean build.

colonarr_gsu did change from static to mod_export along with the get and
set function it includes. vararray_gsu didn't change other than in
being referenced from a module. Looking for other examples, I'm not
really finding any. Modules otherwise only include variables with
access functions that are unique to them.

Oliver


  reply	other threads:[~2021-11-11 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 22:15 Oliver Kiddle
2021-11-01  0:06 ` Oliver Kiddle
2021-11-01  3:11   ` Bart Schaefer
2021-11-06  0:17     ` Oliver Kiddle
2021-11-06 20:53       ` Bart Schaefer
2021-11-28 20:56         ` Oliver Kiddle
2021-11-29  4:31           ` Bart Schaefer
2021-11-09 10:27       ` Jun. T
2021-11-09 21:09         ` Daniel Shahaf
2021-11-11 11:06 ` Jun T
2021-11-11 17:08   ` Oliver Kiddle [this message]
2021-11-12  9:19     ` Jun T

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=93977-1636650510.897657@B71Q.U4fb.k4DR \
    --to=opk@zsh.org \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).