From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] ltp-cap.m4: add libcap version detection && fix compiler error
Date: Mon, 13 May 2019 15:14:51 +0200 [thread overview]
Message-ID: <20190513131451.GA22761@dell5510> (raw)
In-Reply-To: <1557732392-7049-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
Hi Yang,
> Current ltp-cap.m4 defines cap_libs when libcap has
> cap_compare function. This function was introduced by
> libcap-2. It is only used for the two places, and another
> places work fines with libcap-1. So add libcap version
> detection.
Can't we just fix these possible compiler errors for old distros and require
libcap v2? TCONF for very old distros looks OK for me.
libcap-2.00 was released 12 years ago (2007), these distros does not have it:
SLES 10 SP3 [1], RHEL-4.8 [2], Debian 4.0 [3]. Do we really want to care about
these old distros (it looks like only RHEL is supported)?
We also dropped libnuma v1 support (in 2c98cbbaf), v2 was released at similar
date (2008).
Kind regards,
Petr
[1] https://distrowatch.com/table.php?distribution=sle&pkglist=true&version=10-sp3#pkglist
[2] https://distrowatch.com/table.php?distribution=redhat&pkglist=true&version=rhel-4.8#pkglist
[3] https://distrowatch.com/table.php?distribution=debian&pkglist=true&version=4.0#pkglist
next prev parent reply other threads:[~2019-05-13 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 7:26 [LTP] [PATCH] ltp-cap.m4: add libcap version detection && fix compiler error Yang Xu
2019-05-13 13:14 ` Petr Vorel [this message]
2019-05-14 5:24 ` xuyang
2019-05-14 12:01 ` Petr Vorel
2019-05-15 9:01 ` xuyang
2019-05-15 14:37 ` Petr Vorel
2019-05-16 6:44 ` xuyang
2019-05-16 6:52 ` [LTP] [PATCH v2] security: add missing PR_CAPBSET_READ/PR_CAPBSET_DROP check Yang Xu
2019-06-20 11:49 ` Petr Vorel
2019-06-21 2:01 ` Yang Xu
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=20190513131451.GA22761@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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