All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 01/27] libxcrypt-compat: upgrade 4.4.19 -> 4.4.20
Date: Mon, 17 May 2021 10:07:15 +0200	[thread overview]
Message-ID: <CANNYZj-EA8WJoysLgVwaXbg2GTAygXxQDjkA_k2vL5433NSt-Q@mail.gmail.com> (raw)
In-Reply-To: <20210516223247.2401235-1-richard.purdie@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 3575 bytes --]

The main libxcrypt recipe was overlooked?

Alex

On Mon, 17 May 2021 at 00:33, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  .../libxcrypt/files/fix_cflags_handling.patch   | 17 +++++++++++++----
>  ...pat_4.4.19.bb => libxcrypt-compat_4.4.20.bb} |  0
>  meta/recipes-core/libxcrypt/libxcrypt.inc       |  2 +-
>  3 files changed, 14 insertions(+), 5 deletions(-)
>  rename meta/recipes-core/libxcrypt/{libxcrypt-compat_4.4.19.bb =>
> libxcrypt-compat_4.4.20.bb} (100%)
>
> diff --git a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> index 5448fe0fa69..0772998c722 100644
> --- a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> +++ b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> @@ -1,3 +1,8 @@
> +From fd9a46695594c3cd836ecb7d959f03f605e69a2f Mon Sep 17 00:00:00 2001
> +From: Richard Purdie <richard.purdie@linuxfoundation.org>
> +Date: Fri, 30 Apr 2021 10:35:02 +0100
> +Subject: [PATCH] libxcrypt: Update to 4.4.19 release and fix symbol
> version
> +
>  If you pass CFLAGS with a leading space, " " gets passed to popen and
> convinces
>  gcc to try and open a file called " ". This results in a confusing error
> message
>  like:
> @@ -9,8 +14,12 @@ Avoid this by stripping empty elements out of CFLAGS.
>  Upstream-Status: Submitted [
> https://github.com/besser82/libxcrypt/pull/126]
>  Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> -Index: a/build-aux/compute-symver-floor
> -===================================================================
> +---
> + build-aux/compute-symver-floor | 2 ++
> + 1 file changed, 2 insertions(+)
> +
> +diff --git a/build-aux/compute-symver-floor
> b/build-aux/compute-symver-floor
> +index 4ec82e1..8117342 100644
>  --- a/build-aux/compute-symver-floor
>  +++ b/build-aux/compute-symver-floor
>  @@ -36,6 +36,8 @@ sub preprocessor_check {
> @@ -20,5 +29,5 @@ Index: a/build-aux/compute-symver-floor
>  +        # Remove empty elements, particularly leading ones which cause
> issues with popen below
>  +        @CFLAGS = grep {$_} @CFLAGS;
>
> -         # We call ensure_C_locale here, not from the main section,
> -         # because this sub might not get called at all, in which
> +         # Remove empty elements, particularly leading ones which
> +         # cause issues with popen below.
> diff --git a/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.19.bb
> b/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.20.bb
> similarity index 100%
> rename from meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.19.bb
> rename to meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.20.bb
> diff --git a/meta/recipes-core/libxcrypt/libxcrypt.inc
> b/meta/recipes-core/libxcrypt/libxcrypt.inc
> index 694e55546f0..c16068c1614 100644
> --- a/meta/recipes-core/libxcrypt/libxcrypt.inc
> +++ b/meta/recipes-core/libxcrypt/libxcrypt.inc
> @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM =
> "file://LICENSING;md5=afed27a72ae2a8075978299eebaa1f5d \
>  inherit autotools pkgconfig
>
>  SRC_URI = "git://github.com/besser82/libxcrypt.git;branch=${SRCBRANCH}
> <http://github.com/besser82/libxcrypt.git;branch=$%7BSRCBRANCH%7D>"
> -SRCREV = "c79119414d7e30017d7b49566e7e4ea35112bdc8"
> +SRCREV = "e73ff0137de5152e69e8abb0bd260541804dfe5a"
>  SRCBRANCH ?= "develop"
>
>  SRC_URI += "file://fix_cflags_handling.patch"
> --
> 2.30.2
>
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 5147 bytes --]

  parent reply	other threads:[~2021-05-17  8:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 22:32 [PATCH 01/27] libxcrypt-compat: upgrade 4.4.19 -> 4.4.20 Richard Purdie
2021-05-16 22:32 ` [PATCH 02/27] ofono: upgrade 1.31 -> 1.32 Richard Purdie
2021-05-16 22:32 ` [PATCH 03/27] libnss-mdns: upgrade 0.14.1 -> 0.15 Richard Purdie
2021-05-16 22:32 ` [PATCH 04/27] python3-git: upgrade 3.1.14 -> 3.1.17 Richard Purdie
2021-05-16 22:32 ` [PATCH 05/27] bind: upgrade 9.16.13 -> 9.16.15 Richard Purdie
2021-05-16 22:32 ` [PATCH 06/27] vala: upgrade 0.52.2 -> 0.52.3 Richard Purdie
2021-05-16 22:32 ` [PATCH 07/27] libjpeg-turbo: upgrade 2.0.6 -> 2.1.0 Richard Purdie
2021-05-16 22:32 ` [PATCH 08/27] btrfs-tools: upgrade 5.12 -> 5.12.1 Richard Purdie
2021-05-16 22:32 ` [PATCH 09/27] python3-hypothesis: upgrade 6.9.1 -> 6.12.0 Richard Purdie
2021-05-16 22:32 ` [PATCH 10/27] python3-numpy: upgrade 1.20.2 -> 1.20.3 Richard Purdie
2021-05-16 22:32 ` [PATCH 11/27] python3-setuptools: upgrade 56.0.0 -> 56.2.0 Richard Purdie
2021-05-17 16:26   ` [OE-core] " Khem Raj
2021-05-17 16:51     ` Richard Purdie
2021-05-16 22:32 ` [PATCH 12/27] gtk+3: upgrade 3.24.28 -> 3.24.29 Richard Purdie
2021-05-16 22:32 ` [PATCH 13/27] sudo: upgrade 1.9.6p1 -> 1.9.7 Richard Purdie
2021-05-16 22:32 ` [PATCH 14/27] stress-ng: upgrade 0.12.06 -> 0.12.08 Richard Purdie
2021-05-16 22:32 ` [PATCH 15/27] less: upgrade 581 -> 586 Richard Purdie
2021-05-16 22:32 ` [PATCH 16/27] libtirpc: upgrade 1.3.1 -> 1.3.2 Richard Purdie
2021-05-16 22:32 ` [PATCH 17/27] libinput: upgrade 1.17.1 -> 1.17.2 Richard Purdie
2021-05-16 22:32 ` [PATCH 18/27] zstd: upgrade 1.4.9 -> 1.5.0 Richard Purdie
2021-05-26  8:02   ` [OE-core] " Khem Raj
2021-05-16 22:32 ` [PATCH 19/27] hdparm: upgrade 9.61 -> 9.62 Richard Purdie
2021-05-16 22:32 ` [PATCH 20/27] libxkbcommon: upgrade 1.2.1 -> 1.3.0 Richard Purdie
2021-05-16 22:32 ` [PATCH 21/27] spirv-tools: upgrade 2020.7 -> 2021.1 Richard Purdie
2021-05-16 22:32 ` [PATCH 22/27] diffoscope: upgrade 172 -> 175 Richard Purdie
2021-05-16 22:32 ` [PATCH 23/27] mpg123: upgrade 1.26.5 -> 1.27.2 Richard Purdie
2021-05-16 22:32 ` [PATCH 24/27] sqlite3: upgrade 3.35.3 -> 3.35.5 Richard Purdie
2021-05-16 22:32 ` [PATCH 25/27] wayland-protocols: upgrade 1.20 -> 1.21 Richard Purdie
2021-05-16 22:32 ` [PATCH 26/27] shaderc: upgrade 2020.5 -> 2021.0 Richard Purdie
2021-05-16 22:32 ` [PATCH 27/27] wpebackend-fdo: upgrade 1.8.3 -> 1.8.4 Richard Purdie
2021-05-17  8:07 ` Alexander Kanavin [this message]
2021-05-17 16:52   ` [OE-core] [PATCH 01/27] libxcrypt-compat: upgrade 4.4.19 -> 4.4.20 Richard Purdie

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=CANNYZj-EA8WJoysLgVwaXbg2GTAygXxQDjkA_k2vL5433NSt-Q@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.