From: Eryu Guan <guaneryu@gmail.com>
To: jeffm@suse.com
Cc: xfstests list <fstests@vger.kernel.org>,
Luis Rodriguez <mcgrof@suse.com>
Subject: Re: [PATCH 0/4] fstests: GDBM detection cleanup
Date: Fri, 23 Mar 2018 11:30:33 +0800 [thread overview]
Message-ID: <20180323033033.GX30836@localhost.localdomain> (raw)
In-Reply-To: <20180315215455.8245-1-jeffm@suse.com>
On Thu, Mar 15, 2018 at 05:54:51PM -0400, jeffm@suse.com wrote:
> From: Jeff Mahoney <jeffm@suse.com>
>
> Commit 2353022 (build: update AC_PACKAGE_WANT_GDBM() and src/dbtest.c
> to build) fixed building on newer SUSE systems but broke older ones. Where
> we used to skip building src/dbtest on SLES systems, now we'd fail
> to build on SLES11. The reason was that we were now detecting
> ndbm.h but also including gdbm.h, which doesn't work on older systems due
> to both defining the datum type. It turns out that no system needs
> gdbm.h at all.
>
> This series cleans up the macros and fixes detection for all systems that
> only have /usr/include/ndbm.h.
Thanks for the fixes and cleanups! I tested them on Fedora 27, RHEL7 and
Debian stretch, with/without gdbm devel package installed, all worked
fine. But I don't have SUSE systems by hand, I assume you've tested them
successfully.
Thanks,
Eryu
next prev parent reply other threads:[~2018-03-23 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 21:54 [PATCH 0/4] fstests: GDBM detection cleanup jeffm
2018-03-15 21:54 ` [PATCH 1/4] build: remove dead AC_PACKAGE_WANT_NDBM macro jeffm
2018-03-15 21:54 ` [PATCH 2/4] build: AC_PACKAGE_WANT_GDBM, fall back to compat if libgdbm detection fails jeffm
2018-03-15 21:54 ` [PATCH 3/4] build: clean up AC_PACKAGE_WANT_GDBM jeffm
2018-03-15 21:54 ` [PATCH 4/4] build: fix <ndbm.h> detection in AC_PACKAGE_WANT_GDBM jeffm
2018-03-23 3:30 ` Eryu Guan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-15 21:53 [PATCH 0/4] fstests: GDBM detection cleanup jeffm
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=20180323033033.GX30836@localhost.localdomain \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=jeffm@suse.com \
--cc=mcgrof@suse.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