From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>, Cedric Ware <cedric.ware__bml@normalesup.org>
Subject: Re: [PATCH] Enable sub-second timeout in zsystem flock
Date: Mon, 6 Jan 2020 17:36:11 +0000 [thread overview]
Message-ID: <1578332171.4786.3.camel@samsung.com> (raw)
In-Reply-To: <20200106173030.eb2pg4rhhgysh35r@phare.normalesup.org>
On Mon, 2020-01-06 at 18:30 +0100, Cedric Ware wrote:
> Also, I assumed that zlong was at least 64-bit; can it happen that it
> be only 32-bit on some systems? That would be a problem to implement
> the microsecond clock function.
That shouldn't happen unless the configuration script can't actually
find a 64-bit type, implying either the compiler doesn't support it or
it's not using standard types. I think you can reasonably consider that
such a failure on a system that actually does support 64-bit integers
isn't your problem.
pws
next prev parent reply other threads:[~2020-01-06 17:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 20:35 Cedric Ware
2019-07-29 22:25 ` Bart Schaefer
2020-01-04 18:47 ` Cedric Ware
2020-01-05 18:42 ` dana
2020-01-05 21:49 ` dana
2020-01-06 17:30 ` Cedric Ware
2020-01-06 17:36 ` Peter Stephenson [this message]
2020-01-07 3:48 ` dana
2020-01-11 15:41 ` Cedric Ware
2020-01-11 19:36 ` dana
2020-01-12 4:25 ` dana
2020-03-08 18:39 ` Cedric Ware
2020-03-12 18:46 ` dana
2020-03-12 19:13 ` dana
2020-03-14 21:04 ` Cedric Ware
2020-03-15 0:50 ` Daniel Shahaf
2020-03-15 1:04 ` dana
2020-03-15 16:03 ` Cedric Ware
2020-03-15 16:54 ` Daniel Shahaf
2020-03-15 17:35 ` Peter Stephenson
2020-03-15 18:36 ` Cedric Ware
2020-03-15 19:13 ` Daniel Shahaf
2020-04-13 21:34 ` Cedric Ware
2020-04-14 11:47 ` Daniel Shahaf
2020-04-14 20:21 ` Cedric Ware
2020-04-15 1:15 ` Daniel Shahaf
2020-04-15 2:05 ` dana
2020-04-16 4:24 ` Daniel Shahaf
2020-04-18 16:32 ` Cedric Ware
2020-04-20 17:28 ` dana
2020-04-20 22:17 ` Cedric Ware
2020-03-15 1:04 ` Daniel Shahaf
2020-03-13 14:26 ` dana
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=1578332171.4786.3.camel@samsung.com \
--to=p.stephenson@samsung.com \
--cc=cedric.ware__bml@normalesup.org \
--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).