From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai.kang@windriver.com, ross.burton@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP
Date: Fri, 18 Jan 2019 11:02:10 +0000 [thread overview]
Message-ID: <b561f725baace2efee3e30b5343cf1102319dcea.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190117071227.57387-1-kai.kang@windriver.com>
On Thu, 2019-01-17 at 02:12 -0500, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> Reset default value of DEBUG_PREFIX_MAP with '-fdebug-prefix-map'.
> Specifying -fdebug-prefix-map is equivalent to specifying all the
> individual -f*-prefix-map options which means including
> -fmacro-prefix-map and -fdebug-prefix-map currently. Option
> -fmacro-prefix-map helps to avoid buildpaths qa warnings which caused
> by __FILE__ macro expansion for packages such as llvm and librepo.
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta/conf/bitbake.conf | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
I like the idea of the patch a lot. Unfortunately it causes an oe-
selftest failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/131
in the go toolchain.
oe-selftest -r gotoolchain.oeGoToolchainSelfTest.test_go_dep_build
should reproduce.
Cheers,
Richard
next prev parent reply other threads:[~2019-01-18 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 7:12 [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP kai.kang
2019-01-17 7:56 ` [PATCH] libidn2: fix buildpaths qa warning kai.kang
2019-01-17 14:34 ` [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP Dan McGregor
2019-01-17 15:19 ` Christopher Larson
2019-01-17 15:19 ` Christopher Larson
2019-01-18 1:29 ` Kang Kai
2019-01-18 11:02 ` Richard Purdie [this message]
2019-01-18 11:15 ` Richard Purdie
2019-01-18 17:55 ` Khem Raj
2019-01-18 20:43 ` Burton, Ross
2019-01-18 20:54 ` Khem Raj
2019-01-21 2:12 ` Kang Kai
2019-01-21 2:17 ` Khem Raj
2019-01-21 2:18 ` Kang 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=b561f725baace2efee3e30b5343cf1102319dcea.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox