From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai <kai.kang@windriver.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] binutils: update USE_ALTERNATIVES_FOR for symlink files
Date: Mon, 12 Sep 2022 15:58:23 +0100 [thread overview]
Message-ID: <25a7f967e61230b78da3b59dd687e82aca414f82.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220911084756.10315-1-kai.kang@windriver.com>
On Sun, 2022-09-11 at 16:47 +0800, kai wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> It provides more binary files by binutils 2.39. Then add them to
> USE_ALTERNATIVES_FOR as others to handle symlink files via
> update-alternative mechanism.
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta/recipes-devtools/binutils/binutils.inc | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta/recipes-devtools/binutils/binutils.inc b/meta/recipes-devtools/binutils/binutils.inc
> index 789c8bec21..9d33a64371 100644
> --- a/meta/recipes-devtools/binutils/binutils.inc
> +++ b/meta/recipes-devtools/binutils/binutils.inc
> @@ -47,7 +47,13 @@ USE_ALTERNATIVES_FOR = " \
> as \
> c++filt \
> elfedit \
> + gp-archive \
> + gp-collect-app \
> + gp-display-html \
> + gp-display-src \
> + gp-display-text \
> gprof \
> + gprofng \
> ld \
> ld.bfd \
> ${LDGOLD_ALTS} \
This throws tons of warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4219
e.g.:
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/5896/steps/12/logs/warnings
but many more.
Cheers,
Richard
next prev parent reply other threads:[~2022-09-12 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 8:47 [PATCH] binutils: update USE_ALTERNATIVES_FOR for symlink files kai.kang
2022-09-12 14:58 ` Richard Purdie [this message]
2022-09-14 0:51 ` [OE-core] " Kai
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=25a7f967e61230b78da3b59dd687e82aca414f82.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox