mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] libcap: Version bump 2.51 -> 2.62.
Date: Thu, 6 Jan 2022 11:32:59 +0100	[thread overview]
Message-ID: <YdbFW2j4+wynFaDV@pengutronix.de> (raw)
In-Reply-To: <20220105131337.4155479-1-christian.melki@t2data.com>

On Wed, Jan 05, 2022 at 02:13:37PM +0100, Christian Melki wrote:
> Update posix capability library.
> 
> Change CC only directive to CROSS_COMPILE so that the new version can
> build properly with cross builds.
> 
> For host-libcap, change BUILD_GPERF to USE_GPERF, as the former is now a
> reserved word.

'ptxdist lint' reports:

[...]
Checking patch directories ...
Unused patch dir 'master.mol-next.v7a/i/lib/p/patches/libcap-2.51'.
[...]

Please take a look at the documentation[1]. It describes what checks you
should run when submitting patches in general and for version bumps
specifically.

Michael

[1] https://www.ptxdist.org/doc/contributing.html


> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
>  rules/host-libcap.make | 2 +-
>  rules/libcap.make      | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/rules/host-libcap.make b/rules/host-libcap.make
> index 2faae99c3..695ce6c44 100644
> --- a/rules/host-libcap.make
> +++ b/rules/host-libcap.make
> @@ -19,7 +19,7 @@ HOST_PACKAGES-$(PTXCONF_HOST_LIBCAP) += host-libcap
>  HOST_LIBCAP_MAKE_OPT := \
>  	prefix= \
>  	lib=lib \
> -	BUILD_GPERF=no \
> +	USE_GPERF=no \
>  	PAM_CAP=no \
>  	GOLANG=no \
>  	LIBATTR=no \
> diff --git a/rules/libcap.make b/rules/libcap.make
> index 5ed11b1f3..df1eeef16 100644
> --- a/rules/libcap.make
> +++ b/rules/libcap.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBCAP) += libcap
>  #
>  # Paths and names
>  #
> -LIBCAP_VERSION	:= 2.51
> -LIBCAP_MD5	:= 4c9febc1bf0afca6a4d9f86fcdb6d900
> +LIBCAP_VERSION	:= 2.62
> +LIBCAP_MD5	:= 342c7560ed2103899f6914d1de75a89f
>  LIBCAP		:= libcap-$(LIBCAP_VERSION)
>  LIBCAP_SUFFIX	:= tar.xz
>  LIBCAP_URL	:= \
> @@ -31,7 +31,7 @@ LIBCAP_LICENSE_FILES := file://License;md5=e2370ba375efe9e1a095c26d37e483b8
>  
>  LIBCAP_MAKE_OPT	:= \
>  	prefix=/usr lib=$(CROSS_LIB_DIR) \
> -	CC=$(CROSS_CC) \
> +	CROSS_COMPILE=$(COMPILER_PREFIX) \
>  	BUILD_CC=$(HOSTCC) \
>  	DYNAMIC=yes \
>  	GOLANG=no \
> -- 
> 2.30.2
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2022-01-06 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 13:13 Christian Melki
2022-01-06 10:32 ` Michael Olbrich [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=YdbFW2j4+wynFaDV@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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