public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/nfs-utils/files/, net-fs/nfs-utils/
Date: Mon, 29 Jan 2024 11:03:04 +0000 (UTC)	[thread overview]
Message-ID: <1706526117.c38258f864e03a8d09402f3b484c789a857e665d.soap@gentoo> (raw)

commit:     c38258f864e03a8d09402f3b484c789a857e665d
Author:     David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 29 11:01:57 2024 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Mon Jan 29 11:01:57 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c38258f8

net-fs/nfs-utils: fix C99 inline semantics

Closes: https://bugs.gentoo.org/922958
Signed-off-by: David Seifert <soap <AT> gentoo.org>

 .../files/nfs-utils-2.6.4-C99-inline.patch         | 26 ++++++++++++++++++++++
 net-fs/nfs-utils/nfs-utils-2.6.4-r3.ebuild         |  1 +
 2 files changed, 27 insertions(+)

diff --git a/net-fs/nfs-utils/files/nfs-utils-2.6.4-C99-inline.patch b/net-fs/nfs-utils/files/nfs-utils-2.6.4-C99-inline.patch
new file mode 100644
index 000000000000..2797249523f6
--- /dev/null
+++ b/net-fs/nfs-utils/files/nfs-utils-2.6.4-C99-inline.patch
@@ -0,0 +1,26 @@
+C99 `inline` is not guaranteed to emit an external definition
+https://www.greenend.org.uk/rjk/tech/inline.html
+Bug: https://bugs.gentoo.org/922958
+
+--- a/utils/exportd/exportd.c
++++ b/utils/exportd/exportd.c
+@@ -53,7 +53,7 @@
+  */
+ inline static void set_signals(void);
+ 
+-inline void
++inline static void
+ cleanup_lockfiles (void)
+ {
+ 	unlink(etab.lockfn);
+--- a/utils/mountd/mountd.c
++++ b/utils/mountd/mountd.c
+@@ -111,7 +111,7 @@
+ 	nfs_svc_unregister(MOUNTPROG, MOUNTVERS_NFSV3);
+ }
+ 
+-static void
++inline static void
+ cleanup_lockfiles (void)
+ {
+ 	unlink(etab.lockfn);

diff --git a/net-fs/nfs-utils/nfs-utils-2.6.4-r3.ebuild b/net-fs/nfs-utils/nfs-utils-2.6.4-r3.ebuild
index 993fead7ae7c..1a00c46a24df 100644
--- a/net-fs/nfs-utils/nfs-utils-2.6.4-r3.ebuild
+++ b/net-fs/nfs-utils/nfs-utils-2.6.4-r3.ebuild
@@ -73,6 +73,7 @@ PATCHES=(
 	"${FILESDIR}"/${PN}-2.5.2-no-werror.patch
 	"${FILESDIR}"/${PN}-udev-sysctl.patch
 	"${FILESDIR}"/${P}-includes.patch
+	"${FILESDIR}"/${P}-C99-inline.patch
 )
 
 pkg_setup() {


             reply	other threads:[~2024-01-29 11:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 11:03 David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 10:36 [gentoo-commits] repo/gentoo:master commit in: net-fs/nfs-utils/files/, net-fs/nfs-utils/ David Seifert
2024-02-16 19:33 Mike Gilbert
2023-06-03  0:47 Mike Gilbert
2022-09-16 21:54 Sam James
2021-11-30 10:45 David Seifert
2021-10-09  5:19 Sam James
2021-08-19 18:37 David Seifert
2021-01-05 20:06 Andreas K. Hüttel
2019-10-30 16:18 Lars Wendler
2019-09-22 18:34 Matt Turner
2019-05-11 21:03 Lars Wendler
2019-04-20 17:35 Lars Wendler
2018-06-19  5:58 Mike Frysinger
2018-05-28 10:35 Lars Wendler
2017-12-21 15:56 Lars Wendler

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=1706526117.c38258f864e03a8d09402f3b484c789a857e665d.soap@gentoo \
    --to=soap@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox