From: David Sterba <dsterba@suse.cz>
To: Pierre Labastie <pierre.labastie@neuf.fr>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs-progs: build system: Fix the test for EXT4_EPOCH_MASK
Date: Mon, 15 Mar 2021 15:53:24 +0100 [thread overview]
Message-ID: <20210315145324.GU7604@twin.jikos.cz> (raw)
In-Reply-To: <20210314184913.5689-1-pierre.labastie@neuf.fr>
On Sun, Mar 14, 2021 at 07:49:13PM +0100, Pierre Labastie wrote:
> After sending the first version of the patch, I realized that it
> was flawed, because of some formatting by the MUA. It took me
> some time to set up an MTA so that git send-email works. Now the
> patch should apply cleanly. Please remove the present paragraph by using
> git am -c. Apologies for the inconvenience(s).
> -- >8 --
> Commit b3df561fbf has introduced the ability to convert extended
> inode time precision on ext4, but this breaks builds on older distros,
> where ext4 does not have the nsec time precision.
>
> Commit c615287cc tried to fix that by testing the availability of
> the EXT4_EPOCH_MASK macro, but the test is not complete.
>
> This patch aims at fixing the macro test, and changes the
> name of the associated HAVE_ macro, since the logic is reverted.
>
> This fixes #353 when ext4 has nsec time precision. Note that
> the test fails when ext4 does not have the nsec time precision.
> Maybe the test shouldn't be run in that case?
>
> Issue: #353
> Signed-off-by: Pierre Labastie <pierre.labastie@neuf.fr>
> ---
> configure.ac | 8 ++++----
> convert/source-ext2.c | 6 +++---
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 612a3f87..dd6a5de7 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -251,10 +251,10 @@ else
> AC_DEFINE([HAVE_OWN_FIEMAP_EXTENT_SHARED_DEFINE], [0], [We did not define FIEMAP_EXTENT_SHARED])
> fi
>
> -HAVE_OWN_EXT4_EPOCH_MASK_DEFINE=0
> -AX_CHECK_DEFINE([ext2fs/ext2_fs.h], [EXT4_EPOCH_MASK], [],
> - [HAVE_OWN_EXT4_EPOCH_MASK_DEFINE=1
> - AC_MSG_WARN([no definition of EXT4_EPOCH_MASK found, probably old e2fsprogs, will use own definition, no 64bit time precision of converted images])])
> +AX_CHECK_DEFINE([ext2fs/ext2_fs.h], [EXT4_EPOCH_MASK],
> + [AC_DEFINE([HAVE_EXT4_EPOCH_MASK_DEFINE], [1],
> + [Define to 1 if e2fsprogs defines EXT4_EPOCH_MASK])],
> + [AC_MSG_WARN([no definition of EXT4_EPOCH_MASK found, probably old e2fsprogs, will use own definition, no 64bit time precision of converted images])])
Inlining the AC_DEFINE to the check will skip defining the macro in case
the EXT4_EPOCH_MASK does not exist and then the C #if won't work.
HAVE_EXT4_EPOCH_MASK_DEFINE=0
AX_CHECK_DEFINE(...
HAVE_EXT4_EPOCH_MASK_DEFINE=1,...)
if x"$HAVE_EXT4_EPOCH_MASK_DEFINE"; then
AC_DEFINE([HAVE_EXT4_EPOCH_MASK_DEFINE], [1])
else
AC_DEFINE([HAVE_EXT4_EPOCH_MASK_DEFINE], [0])
fi
This should work, maybe it's not the shortest way to write that but I
can't find anything better.
next prev parent reply other threads:[~2021-03-15 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 21:55 Subject: [PATCH] btrfs-progs: Fix the test for EXT4_EPOCH_MASK Pierre Labastie
2021-03-14 18:49 ` [PATCH v2] btrfs-progs: build system: " Pierre Labastie
2021-03-15 14:53 ` David Sterba [this message]
2021-03-15 22:19 ` Pierre Labastie
2021-03-15 23:18 ` David Sterba
2021-03-15 15:24 ` David Sterba
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=20210315145324.GU7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=pierre.labastie@neuf.fr \
/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