From: Petr Vorel <pvorel@suse.cz>
To: Steve Dickson <steved@redhat.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
linux-nfs@vger.kernel.org, Richard Weinberger <richard@nod.at>
Subject: Re: [nfs-utils 1/2] Fix build failure due to glibc <= 2.24 and check for Linux 3.17+
Date: Fri, 18 Oct 2024 15:43:01 +0200 [thread overview]
Message-ID: <20241018134301.GA310040@pevik> (raw)
In-Reply-To: <622276d1-0566-4b6e-90bc-c6ec3e1da47a@redhat.com>
Hi Steve, Giulio, Richard,
> Hello,
> On 10/26/23 3:47 PM, Petr Vorel wrote:
> > interesting, I yesterday sent patch [1] solving the same problem (although it
> > might not be that obvious from the patchset name). Let's see which one will be
> > taken.
> > Kind regards,
> > Petr
> > [1] https://lore.kernel.org/linux-nfs/20231025205720.GB460410@pevik/T/#m4c02286afae09318f6b95ff837750708d5065cd5
> There are a number of patches in the above link
> Could you please post, in the usual format, that
> fixes the issue.
@Steve IMHO all build failures on glibc <= 2.24 and Linux 3.17+ has been fixed
in f92fd6ca ("support/backend_sqlite.c: Add getrandom() fallback") [1].
I don't see any new issue in the thread which is from 2023.
Are you just double checking if any patch was left on ML?
Or do I miss something (it's Friday maybe I'm just tired)?
@Giulio @Richard feel free to correct me.
Kind regards,
Petr
> tia,
> steved.
[1] https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=f92fd6ca815025c435dabf45da28472ac0aa04a4
next prev parent reply other threads:[~2024-10-18 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 11:45 [nfs-utils 1/2] Fix build failure due to glibc <= 2.24 and check for Linux 3.17+ Giulio Benetti
2023-10-26 11:45 ` [nfs-utils 2/2] Drop unused <sys/random.h> Giulio Benetti
2023-10-26 19:47 ` [nfs-utils 1/2] Fix build failure due to glibc <= 2.24 and check for Linux 3.17+ Petr Vorel
2023-10-26 21:18 ` Giulio Benetti
2024-10-18 13:13 ` Steve Dickson
2024-10-18 13:43 ` Petr Vorel [this message]
2024-10-18 14:37 ` Steve Dickson
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=20241018134301.GA310040@pevik \
--to=pvorel@suse.cz \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.kernel.org \
--cc=richard@nod.at \
--cc=steved@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.