Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake.conf: reset default value of DEBUG_PREFIX_MAP
Date: Mon, 21 Jan 2019 10:18:46 +0800	[thread overview]
Message-ID: <d6f1f3ee-a815-6a93-cb46-5bf9b289eade@windriver.com> (raw)
In-Reply-To: <CAMKF1sqvEN+-_9uU6ZzX=+G=0dp3fKmOBWQ8o1CVXxeLJ_pwYQ@mail.gmail.com>

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



      reply	other threads:[~2019-01-21  2:19 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
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 [this message]

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=d6f1f3ee-a815-6a93-cb46-5bf9b289eade@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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