From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH 1/3] Move readhistfile() after flockhistfile().
Date: Sat, 9 Mar 2019 17:19:35 -0800 [thread overview]
Message-ID: <CAH+w=7ZG4jqwGk17dzN3GU4utEYgeGHwvAfVYyeFP8uZ1EK5+g@mail.gmail.com> (raw)
In-Reply-To: <3228a3e68f2580fc25a9fda9bf7ccf5ce9a73689.camel@fifi.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On Sat, Mar 9, 2019, 12:29 PM Philippe Troin <phil@fifi.org> wrote:
>
> By the way, on a completely unrelated note, on recent version of Fedora
> (running 29 here), I need to configure with CFLAGS=-I/usr/include/tirpc
> or the build fails with:
>
> hashnameddir.c:49:12: fatal error: rpc/types.h: No such file or
> directory
> # include <rpc/types.h>
> ^~~~~~~~~~~~~
>
> Do we need a feature check for libtirpc?
>
I don't know Fedora very well; feedback from the list would be beneficial.
But it sounds to me as though we do.
>
next prev parent reply other threads:[~2019-03-10 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 18:30 Issues with fcntl() history file locking Philippe Troin
2019-02-27 21:27 ` Bart Schaefer
2019-02-28 6:36 ` Philippe Troin
2019-03-09 0:53 ` Philippe Troin
2019-03-09 0:54 ` [PATCH 1/3] Move readhistfile() after flockhistfile() Philippe Troin
2019-03-09 0:54 ` [PATCH 2/3] Factorize the code that unlock the fcntl() lock into funlockhistfile() Philippe Troin
2019-03-09 0:54 ` [PATCH 3/3] Delay closing the history file until the fcntl-lock is released Philippe Troin
[not found] ` <CAH+w=7aUD11M_GYy-FOC5MPGpGXb+o9O_q855OTC32fnSnpshQ@mail.gmail.com>
[not found] ` <82f4a6db638fbfce396e64a45029424185863068.camel@fifi.org>
[not found] ` <CAH+w=7ZS=ke8xHuBaO+hu0-RTtW=GYnG-0MENfBtTsyyp9joyg@mail.gmail.com>
[not found] ` <3228a3e68f2580fc25a9fda9bf7ccf5ce9a73689.camel@fifi.org>
2019-03-10 1:19 ` Bart Schaefer [this message]
2019-03-11 21:04 ` [PATCH 1/3] Move readhistfile() after flockhistfile() Jason L Tibbitts III
2019-03-12 7:55 ` Jun T
2019-03-12 9:52 ` Peter Stephenson
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='CAH+w=7ZG4jqwGk17dzN3GU4utEYgeGHwvAfVYyeFP8uZ1EK5+g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--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).