[PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[kai.kang]

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(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 0bdcd04d74..d20460e845 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -599,9 +599,9 @@ EXTRA_OEMAKE_prepend_task-install = "${PARALLEL_MAKEINST} "
 # Optimization flags.
 ##################################################################
 # Beware: applied last to first
-DEBUG_PREFIX_MAP ?= "-fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
-                     -fdebug-prefix-map=${STAGING_DIR_HOST}= \
-                     -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
+DEBUG_PREFIX_MAP ?= "-ffile-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
+                     -ffile-prefix-map=${STAGING_DIR_HOST}= \
+                     -ffile-prefix-map=${STAGING_DIR_NATIVE}= \
 "
 DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types ${DEBUG_PREFIX_MAP}"
 
-- 
2.20.0

[PATCH] libidn2: fix buildpaths qa warning

[kai.kang]

From: Kai Kang <kai.kang@windriver.com>

Fix buildpaths qa warning of libidn2:

| WARNING: libidn2-2.0.5-r0 do_package_qa: QA Issue: File
| /work/core2-64-poky-linux/libidn2/2.0.5-r0/packages-split/libidn2-dev/usr/lib/pkgconfig/libidn2.pc
| in package contained reference to tmpdir [buildpaths]

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
 meta/recipes-extended/libidn/libidn2_2.0.5.bb | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-extended/libidn/libidn2_2.0.5.bb b/meta/recipes-extended/libidn/libidn2_2.0.5.bb
index 0daf7a6877..da77c4402d 100644
--- a/meta/recipes-extended/libidn/libidn2_2.0.5.bb
+++ b/meta/recipes-extended/libidn/libidn2_2.0.5.bb
@@ -26,4 +26,8 @@ EXTRA_OECONF += "--disable-rpath \
 LICENSE_${PN} = "(GPLv2+ | LGPLv3)"
 LICENSE_${PN}-bin = "GPLv3+"
 
+do_install_append () {
+    sed -i 's#${RECIPE_SYSROOT}##' ${D}${libdir}/pkgconfig/libidn2.pc
+}
+
 BBCLASSEXTEND = "native nativesdk"
-- 
2.20.0

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Dan McGregor]

On Thu, 17 Jan 2019 at 01:13, <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(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 0bdcd04d74..d20460e845 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -599,9 +599,9 @@ EXTRA_OEMAKE_prepend_task-install = "${PARALLEL_MAKEINST} "
>  # Optimization flags.
>  ##################################################################
>  # Beware: applied last to first
> -DEBUG_PREFIX_MAP ?= "-fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
> -                     -fdebug-prefix-map=${STAGING_DIR_HOST}= \
> -                     -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
> +DEBUG_PREFIX_MAP ?= "-ffile-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
> +                     -ffile-prefix-map=${STAGING_DIR_HOST}= \
> +                     -ffile-prefix-map=${STAGING_DIR_NATIVE}= \
>  "
>  DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types ${DEBUG_PREFIX_MAP}"
>

I like the idea of this, but it will break meta-clang until either 1)
https://reviews.llvm.org/D49466 lands, or 2) meta-clang sets its own
DEBUG_PREFIX_MAP.

> --
> 2.20.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]

The commit message doesn’t match what you’re actually doing. "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” I assume you mean "Specifying
-ffile-prefix-map” there.

On Thu, Jan 17, 2019 at 12:13 AM <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(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 0bdcd04d74..d20460e845 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -599,9 +599,9 @@ EXTRA_OEMAKE_prepend_task-install =
> "${PARALLEL_MAKEINST} "
>  # Optimization flags.
>  ##################################################################
>  # Beware: applied last to first
> -DEBUG_PREFIX_MAP ?=
> "-fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
> -                     -fdebug-prefix-map=${STAGING_DIR_HOST}= \
> -                     -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
> +DEBUG_PREFIX_MAP ?=
> "-ffile-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
> +                     -ffile-prefix-map=${STAGING_DIR_HOST}= \
> +                     -ffile-prefix-map=${STAGING_DIR_NATIVE}= \
>  "
>  DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types ${DEBUG_PREFIX_MAP}"
>
> --
> 2.20.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 3265 bytes --]

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 2686 bytes --]

You also aren’t “resetting” anything, I’d suggest clarifying the summary as
well.

On Thu, Jan 17, 2019 at 8:19 AM Christopher Larson <kergoth@gmail.com>
wrote:

> The commit message doesn’t match what you’re actually doing. "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” I assume you mean "Specifying
> -ffile-prefix-map” there.
>
> On Thu, Jan 17, 2019 at 12:13 AM <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(-)
>>
>> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
>> index 0bdcd04d74..d20460e845 100644
>> --- a/meta/conf/bitbake.conf
>> +++ b/meta/conf/bitbake.conf
>> @@ -599,9 +599,9 @@ EXTRA_OEMAKE_prepend_task-install =
>> "${PARALLEL_MAKEINST} "
>>  # Optimization flags.
>>  ##################################################################
>>  # Beware: applied last to first
>> -DEBUG_PREFIX_MAP ?=
>> "-fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
>> -                     -fdebug-prefix-map=${STAGING_DIR_HOST}= \
>> -                     -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
>> +DEBUG_PREFIX_MAP ?=
>> "-ffile-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
>> +                     -ffile-prefix-map=${STAGING_DIR_HOST}= \
>> +                     -ffile-prefix-map=${STAGING_DIR_NATIVE}= \
>>  "
>>  DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types ${DEBUG_PREFIX_MAP}"
>>
>> --
>> 2.20.0
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
> --
> Christopher Larson
> kergoth at gmail dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Senior Software Engineer, Mentor Graphics
>


-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 4100 bytes --]

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Kang Kai]

[-- Attachment #1: Type: text/plain, Size: 2809 bytes --]

On 2019/1/17 下午11:19, Christopher Larson wrote:
> The commit message doesn’t match what you’re actually doing. 
> "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” I 
> assume you mean "Specifying -ffile-prefix-map” there.


Sorry typo here.

Regards,
Kai


>
> On Thu, Jan 17, 2019 at 12:13 AM <kai.kang@windriver.com 
> <mailto:kai.kang@windriver.com>> wrote:
>
>     From: Kai Kang <kai.kang@windriver.com
>     <mailto: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
>     <mailto:kai.kang@windriver.com>>
>     ---
>      meta/conf/bitbake.conf | 6 +++---
>      1 file changed, 3 insertions(+), 3 deletions(-)
>
>     diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
>     index 0bdcd04d74..d20460e845 100644
>     --- a/meta/conf/bitbake.conf
>     +++ b/meta/conf/bitbake.conf
>     @@ -599,9 +599,9 @@ EXTRA_OEMAKE_prepend_task-install =
>     "${PARALLEL_MAKEINST} "
>      # Optimization flags.
>      ##################################################################
>      # Beware: applied last to first
>     -DEBUG_PREFIX_MAP ?=
>     "-fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR}
>     \
>     -                     -fdebug-prefix-map=${STAGING_DIR_HOST}= \
>     -  -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
>     +DEBUG_PREFIX_MAP ?=
>     "-ffile-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR}
>     \
>     +                     -ffile-prefix-map=${STAGING_DIR_HOST}= \
>     +                     -ffile-prefix-map=${STAGING_DIR_NATIVE}= \
>      "
>      DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types
>     ${DEBUG_PREFIX_MAP}"
>
>     -- 
>     2.20.0
>
>     -- 
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> -- 
> Christopher Larson
> kergoth at gmail dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Senior Software Engineer, Mentor Graphics


-- 
Kai Kang


[-- Attachment #2: Type: text/html, Size: 5032 bytes --]

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Richard Purdie]

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

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Richard Purdie]

On Fri, 2019-01-18 at 11:02 +0000, Richard Purdie wrote:
> 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.

There does appear to be another issue:

http://git.yoctoproject.org/cgit.cgi/poky-buildhistory/commit/?h=poky/master-next/qemux86&id=e3195d9809716652546a1ac69a75287ec707e79b

The debug src files appear to be disappearing?

Cheers,

Richard

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Khem Raj]

On Wed, Jan 16, 2019 at 11:13 PM <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(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 0bdcd04d74..d20460e845 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -599,9 +599,9 @@ EXTRA_OEMAKE_prepend_task-install = "${PARALLEL_MAKEINST} "
>  # Optimization flags.
>  ##################################################################
>  # Beware: applied last to first
> -DEBUG_PREFIX_MAP ?= "-fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
> -                     -fdebug-prefix-map=${STAGING_DIR_HOST}= \
> -                     -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
> +DEBUG_PREFIX_MAP ?= "-ffile-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR} \
> +                     -ffile-prefix-map=${STAGING_DIR_HOST}= \
> +                     -ffile-prefix-map=${STAGING_DIR_NATIVE}= \

I am bit concerned about using -ffile-prefix-map here, its gcc only
option so will cause clang to fail

>  "
>  DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types ${DEBUG_PREFIX_MAP}"
>
> --
> 2.20.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Burton, Ross]

On Fri, 18 Jan 2019 at 17:55, Khem Raj <raj.khem@gmail.com> wrote:
> I am bit concerned about using -ffile-prefix-map here, its gcc only
> option so will cause clang to fail

It's almost like we need a toolchain override so this can be gcc-specific...

I've been meaning to do that for about a year now :(

Until then, couldn't meta-clang just override the value from the layer?

Ross

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Khem Raj]

On Fri, Jan 18, 2019 at 12:43 PM Burton, Ross <ross.burton@intel.com> wrote:
>
> On Fri, 18 Jan 2019 at 17:55, Khem Raj <raj.khem@gmail.com> wrote:
> > I am bit concerned about using -ffile-prefix-map here, its gcc only
> > option so will cause clang to fail
>
> It's almost like we need a toolchain override so this can be gcc-specific...
>
> I've been meaning to do that for about a year now :(
>
> Until then, couldn't meta-clang just override the value from the layer?

yes it can, but one by one there are many changes to keep and core becomes
tied to gcc. We should be conscious about it.

>
> Ross

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Kang Kai]

On 2019/1/19 上午4:54, Khem Raj wrote:
> On Fri, Jan 18, 2019 at 12:43 PM Burton, Ross <ross.burton@intel.com> wrote:
>> On Fri, 18 Jan 2019 at 17:55, Khem Raj <raj.khem@gmail.com> wrote:
>>> I am bit concerned about using -ffile-prefix-map here, its gcc only
>>> option so will cause clang to fail
>> It's almost like we need a toolchain override so this can be gcc-specific...
>>
>> I've been meaning to do that for about a year now :(
>>
>> Until then, couldn't meta-clang just override the value from the layer?
> yes it can, but one by one there are many changes to keep and core becomes
> tied to gcc. We should be conscious about it.


 From the link https://reviews.llvm.org/D49466 pasted by Dan, we know 
that clang will support option '-ffile-prefix-map'.
I prefer to override DEBUG_PREFIX_MAP in meta-clang and remove it when 
clang support for '-ffile-prefix-map' implemented.

Regards,
Kai


>
>> Ross


-- 
Kai Kang

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Khem Raj]

On Sun, Jan 20, 2019 at 6:12 PM Kang Kai <Kai.Kang@windriver.com> wrote:
>
> On 2019/1/19 上午4:54, Khem Raj wrote:
> > On Fri, Jan 18, 2019 at 12:43 PM Burton, Ross <ross.burton@intel.com> wrote:
> >> On Fri, 18 Jan 2019 at 17:55, Khem Raj <raj.khem@gmail.com> wrote:
> >>> I am bit concerned about using -ffile-prefix-map here, its gcc only
> >>> option so will cause clang to fail
> >> It's almost like we need a toolchain override so this can be gcc-specific...
> >>
> >> I've been meaning to do that for about a year now :(
> >>
> >> Until then, couldn't meta-clang just override the value from the layer?
> > yes it can, but one by one there are many changes to keep and core becomes
> > tied to gcc. We should be conscious about it.
>
>
>  From the link https://reviews.llvm.org/D49466 pasted by Dan, we know
> that clang will support option '-ffile-prefix-map'.
> I prefer to override DEBUG_PREFIX_MAP in meta-clang and remove it when
> clang support for '-ffile-prefix-map' implemented.

Thats ok, not worried about clang at this point. But the patch itself
was not working last time on gcc either. So if that is fixed we can consider it.

>
> Regards,
> Kai
>
>
> >
> >> Ross
>
>
> --
> Kai Kang
>

Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP

[Kang Kai]

On 2019/1/21 上午10:17, Khem Raj wrote:
> On Sun, Jan 20, 2019 at 6:12 PM Kang Kai <Kai.Kang@windriver.com> wrote:
>> On 2019/1/19 上午4:54, Khem Raj wrote:
>>> On Fri, Jan 18, 2019 at 12:43 PM Burton, Ross <ross.burton@intel.com> wrote:
>>>> On Fri, 18 Jan 2019 at 17:55, Khem Raj <raj.khem@gmail.com> wrote:
>>>>> I am bit concerned about using -ffile-prefix-map here, its gcc only
>>>>> option so will cause clang to fail
>>>> It's almost like we need a toolchain override so this can be gcc-specific...
>>>>
>>>> I've been meaning to do that for about a year now :(
>>>>
>>>> Until then, couldn't meta-clang just override the value from the layer?
>>> yes it can, but one by one there are many changes to keep and core becomes
>>> tied to gcc. We should be conscious about it.
>>
>>   From the link https://reviews.llvm.org/D49466 pasted by Dan, we know
>> that clang will support option '-ffile-prefix-map'.
>> I prefer to override DEBUG_PREFIX_MAP in meta-clang and remove it when
>> clang support for '-ffile-prefix-map' implemented.
> Thats ok, not worried about clang at this point. But the patch itself
> was not working last time on gcc either. So if that is fixed we can consider it.


OK. I am working on the issued pointed by Richard.


>
>> Regards,
>> Kai
>>
>>
>>>> Ross
>>
>> --
>> Kai Kang
>>

-- 
Kai Kang