From: "Denys Dmytriyenko" <denis@denix.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: meta-arm@lists.yoctoproject.org, pbarker@konsulko.com,
wmills@ti.com, richard.purdie@linuxfoundation.org,
daniel.thompson@linaro.org
Subject: Re: [meta-arm] [PATCH v2 1/5] external-arm-toolchain: Remove glibc locale dependency
Date: Fri, 12 Jun 2020 00:14:53 -0400 [thread overview]
Message-ID: <20200612041453.GH17660@denix.org> (raw)
In-Reply-To: <1591796582-5015-2-git-send-email-sumit.garg@linaro.org>
On Wed, Jun 10, 2020 at 07:12:58PM +0530, Sumit Garg wrote:
> Currently external Arm toolchain recipe doesn't provide packages
> corresponding to OE glibc locale recipe. So explicitly remove corresponding
> libc dependencies until we sort out glibc locale packaging rather than
> blocking OE SDK generation which is still useful without glibc locale
> packaging.
I guess we can merge this one for now with the idea of getting back to it
later and trying to properly package gconv libs and locales.
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
Reviewed-by: Denys Dmytriyenko <denys@ti.com>
> ---
> meta-arm-toolchain/conf/distro/include/tcmode-external-arm.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-arm-toolchain/conf/distro/include/tcmode-external-arm.inc b/meta-arm-toolchain/conf/distro/include/tcmode-external-arm.inc
> index 9171380..eee1a51 100644
> --- a/meta-arm-toolchain/conf/distro/include/tcmode-external-arm.inc
> +++ b/meta-arm-toolchain/conf/distro/include/tcmode-external-arm.inc
> @@ -58,6 +58,7 @@ DISTRO_FEATURES_LIBC = "ipv4 ipv6 libc-backtrace libc-big-macros libc-bsd libc-c
> ENABLE_BINARY_LOCALE_GENERATION = "0"
> GLIBC_INTERNAL_USE_BINARY_LOCALE = "precompiled"
> LIBCOVERRIDE = ":libc-glibc"
> +LIBC_DEPENDENCIES_remove = "glibc-gconv-cp1252 glibc-gconv-ibm850 glibc-gconv-iso8859-1 glibc-gconv-iso8859-15 glibc-localedata-i18n"
BTW, avoiding _remove would require adding intermediary variable to OE-Core
just for this sub-list in order to clear it out downstream...
> ERROR_QA[type] ?= "list"
> python toolchain_metadata_setup () {
> --
> 2.7.4
>
>
next prev parent reply other threads:[~2020-06-12 4:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:42 [PATCH v2 0/5] external-arm-toolchain: Add support for SDK generation Sumit Garg
2020-06-10 13:42 ` [PATCH v2 1/5] external-arm-toolchain: Remove glibc locale dependency Sumit Garg
2020-06-12 4:14 ` Denys Dmytriyenko [this message]
2020-06-10 13:42 ` [PATCH v2 2/5] external-arm-toolchain: Refine dev libraries/headers packaging Sumit Garg
2020-06-12 4:23 ` Denys Dmytriyenko
2020-06-12 7:07 ` Sumit Garg
2020-06-12 7:35 ` Denys Dmytriyenko
2020-06-12 8:49 ` Sumit Garg
2020-06-10 13:43 ` [PATCH v2 3/5] external-arm-toolchain: Align glibc packaging to OE TARGET_SYS Sumit Garg
2020-06-12 2:15 ` Denys Dmytriyenko
2020-06-12 5:33 ` Sumit Garg
2020-06-12 6:16 ` Denys Dmytriyenko
2020-06-12 7:12 ` Sumit Garg
2020-06-10 13:43 ` [PATCH v2 4/5] meta-arm-toolchain: Add README Sumit Garg
2020-06-10 13:43 ` [PATCH v2 5/5] external-arm-toolchain: Add package specific licenses Sumit Garg
2020-06-12 4:26 ` Denys Dmytriyenko
2020-06-11 15:12 ` [meta-arm] [PATCH v2 0/5] external-arm-toolchain: Add support for SDK generation Jon Mason
2020-06-12 2:18 ` Denys Dmytriyenko
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=20200612041453.GH17660@denix.org \
--to=denis@denix.org \
--cc=daniel.thompson@linaro.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=pbarker@konsulko.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=sumit.garg@linaro.org \
--cc=wmills@ti.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 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.