Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"liezhi.yang@windriver.com" <liezhi.yang@windriver.com>,
	"raj.khem@gmail.com" <raj.khem@gmail.com>,
	"richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH 1/5] base/bbclass: use target path as compile dir in debugging info
Date: Sat, 30 Jan 2016 09:15:09 +0800	[thread overview]
Message-ID: <56AC0E9D.6050806@windriver.com> (raw)
In-Reply-To: <a17cbe21ef44455c98414ba1a4f1ffdd@XBOX02.axis.com>

On 01/30/2016 01:48 AM, Peter Kjellerstedt wrote:
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Hongxu Jia
>> Sent: den 29 januari 2016 18:36
>> To: openembedded-core@lists.openembedded.org;
>> liezhi.yang@windriver.com; raj.khem@gmail.com;
>> richard.purdie@linuxfoundation.org
>> Subject: [OE-core] [PATCH 1/5] base/bbclass: use target path as compile dir in debugging info
>                                   ^^^^^^^^^^^^
> Change the prefix to "bitbake.conf" to reflect that you now do the
> Change there...

Sorry for the typo

//Hongxu

>
> //Peter
>



  reply	other threads:[~2016-01-30  1:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 17:35 [PATCH v3 0/5]use target path to replace build ones in debugging info Hongxu Jia
2016-01-29 17:35 ` [PATCH 1/5] base/bbclass: use target path as compile dir " Hongxu Jia
2016-01-29 17:48   ` Peter Kjellerstedt
2016-01-30  1:15     ` Hongxu Jia [this message]
2016-01-29 17:35 ` [PATCH 2/5] gcc-5.3.inc/base.bbclass: add gcc option to not record -fdebug-prefix-map to " Hongxu Jia
2016-01-29 17:47   ` Peter Kjellerstedt
2016-01-30  1:25     ` Hongxu Jia
2016-01-30  2:36       ` Khem Raj
2016-01-30 10:57         ` Richard Purdie
2016-02-01 14:01           ` Hongxu Jia
2016-02-01 14:09             ` Richard Purdie
2016-02-01 17:10               ` Khem Raj
2016-02-07 16:17               ` Hongxu Jia
2016-01-30 11:43   ` Phil Blundell
2016-02-20 13:00   ` Martin Jansa
2016-02-20 15:02     ` Khem Raj
2016-02-22  6:44     ` Hongxu Jia
2016-02-22 15:35       ` Martin Jansa
2016-01-29 17:35 ` [PATCH 3/5] mkelfimage: fix target cflags leaks to host Hongxu Jia
2016-01-29 17:35 ` [PATCH 4/5] glibc.inc: do not immediate expand SELECTED_OPTIMIZATION Hongxu Jia
2016-01-30 10:35   ` Phil Blundell
2016-01-29 17:35 ` [PATCH 5/5] systemtap_git.inc: " Hongxu Jia

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=56AC0E9D.6050806@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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