From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-cross-canadian.inc: add INSANE_SKIP_ to avoid build warning
Date: Tue, 26 Jul 2016 17:33:30 +0800 [thread overview]
Message-ID: <57972E6A.5000202@windriver.com> (raw)
In-Reply-To: <1469521360-16641-1-git-send-email-mingli.yu@windriver.com>
Please ignore this patch.
Verified gcc-5.4 and gcc-6.1 and it proves that no same warning exist.
Thanks,
Grace
On 2016年07月26日 16:22, mingli.yu@windriver.com wrote:
> WARNING: QA Issue: gcc-cross-canadian-i586-dbg: found library in wrong location:
> /PATH/sysroots/x86_64-oesdk-linux/usr/libexec/i586-oe-linux/gcc/
> i586-oe-linux/5.2.0/.debug/libcc1.so.0.0.0
>
> This warning is introduced by commit f6e47aa(gcc-target 5.1: fix for libcc1)
>
> Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> (From OE-Core jethro rev: 62c51c4178fb66341498c71c74ce42652568c7fa)
> Signed-off-by: Yue Tao <Yue.Tao@windriver.com>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
> meta/recipes-devtools/gcc/gcc-cross-canadian.inc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-cross-canadian.inc b/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
> index ec1d281..1286179 100644
> --- a/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
> +++ b/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
> @@ -83,6 +83,8 @@ FILES_${PN} = "\
> ${prefix}/${TARGET_SYS}/usr/include/* \
> "
> INSANE_SKIP_${PN} += "dev-so"
> +INSANE_SKIP_${PN} += "libdir"
> +INSANE_SKIP_${PN}-dbg += "libdir"
>
> FILES_${PN}-doc = "\
> ${infodir} \
>
next prev parent reply other threads:[~2016-07-26 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 8:22 [PATCH] gcc-cross-canadian.inc: add INSANE_SKIP_ to avoid build warning mingli.yu
2016-07-26 9:33 ` Yu, Mingli [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 5:48 Li Xin
2016-03-22 9:30 ` Richard Purdie
2016-03-22 10:57 ` Li, Xin
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=57972E6A.5000202@windriver.com \
--to=mingli.yu@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 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.