From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@gmail.com>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [OE-core] [PATCH 10/24] libxcrypt-compat: upgrade 4.4.26 -> 4.4.27
Date: Mon, 03 Jan 2022 17:43:40 +0000 [thread overview]
Message-ID: <7a6436e388ed72f2321bb8fc4228eea365752c0b.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220103161854.301148-10-otavio@ossystems.com.br>
On Mon, 2022-01-03 at 13:18 -0300, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> .../libxcrypt/files/fix_cflags_handling.patch | 11 +-
> .../libxcrypt/libxcrypt-compat_4.4.26.bb | 18 ---
> .../libxcrypt/libxcrypt-compat_4.4.27.bb | 103 ++++++++++++++++++
> meta/recipes-core/libxcrypt/libxcrypt.inc | 4 +-
> 4 files changed, 111 insertions(+), 25 deletions(-)
> delete mode 100644 meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.26.bb
> create mode 100644 meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.27.bb
>
> diff --git a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> index 0772998c72..d979796226 100644
> --- a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> +++ b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch
> @@ -1,7 +1,8 @@
> -From fd9a46695594c3cd836ecb7d959f03f605e69a2f Mon Sep 17 00:00:00 2001
> +From 7b2a0cdc281d94a5782c37ef87040c341447b4b4 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
> +Organization: O.S. Systems Software LTDA.
>
> 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
> @@ -15,13 +16,13 @@ Upstream-Status: Submitted [https://github.com/besser82/libxcrypt/pull/126]
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> ---
> - build-aux/compute-symver-floor | 2 ++
> + build-aux/scripts/compute-symver-floor | 2 ++
> 1 file changed, 2 insertions(+)
>
> -diff --git a/build-aux/compute-symver-floor b/build-aux/compute-symver-floor
> +diff --git a/build-aux/scripts/compute-symver-floor b/build-aux/scripts/compute-symver-floor
> index 4ec82e1..8117342 100644
> ---- a/build-aux/compute-symver-floor
> -+++ b/build-aux/compute-symver-floor
> +--- a/build-aux/scripts/compute-symver-floor
> ++++ b/build-aux/scripts/compute-symver-floor
> @@ -36,6 +36,8 @@ sub preprocessor_check {
> die "C compiler not available\n" unless @CC;
>
> diff --git a/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.26.bb b/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.26.bb
> deleted file mode 100644
> index ec9f9f4fa3..0000000000
> --- a/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.26.bb
> +++ /dev/null
> @@ -1,18 +0,0 @@
> -#
> -# This provides libcrypto.so.1 which contains obsolete APIs, needed for uninative in particular
> -#
> -
> -require libxcrypt.inc
> -
> -PROVIDES = ""
> -AUTO_LIBNAME_PKGS = ""
> -EXCLUDE_FROM_WORLD = "1"
> -
> -API = "--enable-obsolete-api"
> -
> -do_install:append () {
> - rm -rf ${D}${includedir}
> - rm -rf ${D}${libdir}/pkgconfig
> - rm -rf ${D}${datadir}
> -}
> -
> diff --git a/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.27.bb b/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.27.bb
> new file mode 100644
> index 0000000000..fd773fc859
> --- /dev/null
> +++ b/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.27.bb
> @@ -0,0 +1,103 @@
> +# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
> +# The following is the difference between the old and the new license text.
> +# Please update the LICENSE value if needed, and summarize the changes in
> +# the commit message via 'License-Update:' tag.
> +# (example: 'License-Update: copyright years updated.')
> +#
Needs further review!
Cheers,
Richard
next prev parent reply other threads:[~2022-01-03 17:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:18 [PATCH 01/24] acpica: upgrade 20210930 -> 20211217 Otavio Salvador
2022-01-03 16:18 ` [PATCH 02/24] alsa-ucm-conf: upgrade 1.2.6.2 -> 1.2.6.3 Otavio Salvador
2022-01-03 16:18 ` [PATCH 03/24] asciidoc: upgrade 10.0.2 -> 10.1.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 04/24] bind: upgrade 9.16.23 -> 9.16.24 Otavio Salvador
2022-01-03 16:18 ` [PATCH 05/24] e2fsprogs: upgrade 1.46.4 -> 1.46.5 Otavio Salvador
2022-01-03 17:42 ` [OE-core] " Richard Purdie
2022-01-03 18:26 ` Otavio Salvador
2022-01-04 10:44 ` Richard Purdie
2022-01-03 16:18 ` [PATCH 06/24] expat: upgrade 2.4.1 -> 2.4.2 Otavio Salvador
2022-01-03 16:18 ` [PATCH 07/24] gnupg: upgrade 2.3.3 -> 2.3.4 Otavio Salvador
2022-01-03 16:18 ` [PATCH 08/24] kea: upgrade 2.0.0 -> 2.0.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 09/24] libmicrohttpd: upgrade 0.9.73 -> 0.9.75 Otavio Salvador
2022-01-03 16:18 ` [PATCH 10/24] libxcrypt-compat: upgrade 4.4.26 -> 4.4.27 Otavio Salvador
2022-01-03 17:43 ` Richard Purdie [this message]
2022-01-03 16:18 ` [PATCH 11/24] meson: upgrade 0.60.2 -> 0.60.3 Otavio Salvador
2022-01-03 19:09 ` [OE-core] " Alexander Kanavin
2022-01-03 22:19 ` Richard Purdie
2022-01-03 16:18 ` [PATCH 12/24] mmc-utils: upgrade to latest revision Otavio Salvador
2022-01-03 16:18 ` [PATCH 13/24] python3-attrs: upgrade 21.2.0 -> 21.4.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 14/24] python3-cython: upgrade 0.29.25 -> 0.29.26 Otavio Salvador
2022-01-03 16:18 ` [PATCH 15/24] python3-dtschema: upgrade 2021.10 -> 2021.12 Otavio Salvador
2022-01-03 16:18 ` [PATCH 16/24] python3-hypothesis: upgrade 6.31.4 -> 6.34.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 17/24] python3-importlib-metadata: upgrade 4.9.0 -> 4.10.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 18/24] python3-pygments: upgrade 2.10.0 -> 2.11.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 19/24] python3-ruamel-yaml: upgrade 0.17.17 -> 0.17.19 Otavio Salvador
2022-01-03 16:18 ` [PATCH 20/24] python3-setuptools: upgrade 59.5.0 -> 60.2.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 21/24] python3-tomli: upgrade 1.2.2 -> 2.0.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 22/24] python3-zipp: upgrade 3.6.0 -> 3.7.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 23/24] sqlite3: upgrade 3.37.0 -> 3.37.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 24/24] stress-ng: upgrade 0.13.08 -> 0.13.09 Otavio Salvador
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=7a6436e388ed72f2321bb8fc4228eea365752c0b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@gmail.com \
--cc=otavio@ossystems.com.br \
/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