From: "Darrick J. Wong" <djwong@kernel.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] include libgen.h for basename API prototype
Date: Mon, 25 Mar 2024 17:15:15 -0700 [thread overview]
Message-ID: <20240326001515.GD6390@frogsfrogsfrogs> (raw)
In-Reply-To: <20240325170941.3279129-1-raj.khem@gmail.com>
On Mon, Mar 25, 2024 at 10:09:41AM -0700, Khem Raj wrote:
> basename prototype has been removed from string.h from latest musl [1]
> compilers e.g. clang-18 flags the absense of prototype as error. therefore
> include libgen.h for providing it.
>
> [1] https://git.musl-libc.org/cgit/musl/commit/?id=725e17ed6dff4d0cd22487bb64470881e86a92e7
The basename(3) manpage makes reference to glibc's POSIX implementation
modifying the string argument passed in. Is that going to cause
problems with the existing callsites in xfsdump?
--D
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> common/main.c | 1 +
> invutil/invidx.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/common/main.c b/common/main.c
> index 1db07d4..ca3b7d4 100644
> --- a/common/main.c
> +++ b/common/main.c
> @@ -16,6 +16,7 @@
> * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
> */
>
> +#include <libgen.h>
> #include <stdio.h>
> #include <unistd.h>
> #include <stdlib.h>
> diff --git a/invutil/invidx.c b/invutil/invidx.c
> index 5874e8d..c4e2e21 100644
> --- a/invutil/invidx.c
> +++ b/invutil/invidx.c
> @@ -19,6 +19,7 @@
> #include <xfs/xfs.h>
> #include <xfs/jdm.h>
>
> +#include <libgen.h>
> #include <stdio.h>
> #include <fcntl.h>
> #include <unistd.h>
> --
> 2.44.0
>
>
prev parent reply other threads:[~2024-03-26 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 17:09 [PATCH] include libgen.h for basename API prototype Khem Raj
2024-03-26 0:15 ` Darrick J. Wong [this message]
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=20240326001515.GD6390@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox