public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Matt Madison <matt@madison.systems>
To: openembedded-core@lists.openembedded.org
Cc: Matt Madison <matt@madison.systems>
Subject: [PATCH][pseudo] ports/linux: add wrapper for statvfs64
Date: Mon, 29 Jan 2024 08:26:15 -0800	[thread overview]
Message-ID: <20240129162615.3724802-1-matt@madison.systems> (raw)

rpm 4.19 now builds with LFS64 support enabled by default,
so it calls statvfs64() to get the space available on the
filesystem it is installing packages into.  Add a wrapper
for this call so the right filesystem is used.

Signed-off-by: Matt Madison <matt@madison.systems>
---
 ports/linux/statvfs/guts/statvfs64.c | 15 +++++++++++++++
 ports/linux/statvfs/wrapfuncs.in     |  1 +
 2 files changed, 16 insertions(+)
 create mode 100644 ports/linux/statvfs/guts/statvfs64.c

diff --git a/ports/linux/statvfs/guts/statvfs64.c b/ports/linux/statvfs/guts/statvfs64.c
new file mode 100644
index 0000000..856d3db
--- /dev/null
+++ b/ports/linux/statvfs/guts/statvfs64.c
@@ -0,0 +1,15 @@
+/*
+ * Copyright (c) 2018 Wind River Systems; see
+ * guts/COPYRIGHT for information.
+ *
+ * SPDX-License-Identifier: LGPL-2.1-only
+ *
+ * int statvfs64(const char *path, struct statvfs64 *buf)
+ *	int rc = -1;
+ */
+
+	rc = real_statvfs64(path, buf);
+
+/*	return rc;
+ * }
+ */
diff --git a/ports/linux/statvfs/wrapfuncs.in b/ports/linux/statvfs/wrapfuncs.in
index 1afb64d..6a59660 100644
--- a/ports/linux/statvfs/wrapfuncs.in
+++ b/ports/linux/statvfs/wrapfuncs.in
@@ -1 +1,2 @@
 int statvfs(const char *path, struct statvfs *buf);
+int statvfs64(const char *path, struct statvfs64 *buf);
-- 
2.34.1



             reply	other threads:[~2024-01-29 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 16:26 Matt Madison [this message]
2024-01-29 16:48 ` [OE-core] [PATCH][pseudo] ports/linux: add wrapper for statvfs64 Khem Raj
2024-01-29 18:03   ` Matt Madison
2024-01-29 18:16     ` Khem Raj

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=20240129162615.3724802-1-matt@madison.systems \
    --to=matt@madison.systems \
    --cc=openembedded-core@lists.openembedded.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