From: Junling Zheng <zhengjunling@huawei.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gmp: remove referencing paths from the build host
Date: Tue, 21 Apr 2015 09:06:24 +0800 [thread overview]
Message-ID: <5535A290.10502@huawei.com> (raw)
In-Reply-To: <1429542910.26983.13.camel@linuxfoundation.org>
On 2015/4/20 23:15, Richard Purdie wrote:
> On Mon, 2015-04-20 at 09:30 +0800, Junling Zheng wrote:
>> On 2015/4/18 2:24, Andre McCurdy wrote:
>>> On Fri, Apr 17, 2015 at 1:50 AM, Junling Zheng <zhengjunling@huawei.com> wrote:
>>>> Currently ${D}${includedir}/gmp.h references the path of build host
>>>> incorrectly, remove it.
>>>>
>>>> Signed-off-by: Junling Zheng <zhengjunling@huawei.com>
>>>> ---
>>>> meta/recipes-support/gmp/gmp.inc | 4 ++++
>>>> 1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/meta/recipes-support/gmp/gmp.inc b/meta/recipes-support/gmp/gmp.inc
>>>> index 558ee06..a80b356 100644
>>>> --- a/meta/recipes-support/gmp/gmp.inc
>>>> +++ b/meta/recipes-support/gmp/gmp.inc
>>>> @@ -26,4 +26,8 @@ EXTRA_OECONF += " --enable-cxx=detect"
>>>> PACKAGES =+ "libgmpxx"
>>>> FILES_libgmpxx = "${libdir}/libgmpxx${SOLIBS}"
>>>>
>>>> +do_install_append_class-target() {
>>>> + sed -i "s+--sysroot=${STAGING_DIR_HOST}++g" ${D}${includedir}/gmp.h
>>>> +}
>>>
>>> It's possible that STAGING_DIR_HOST could contain '+' characters, so
>>> '|' would be a safer sed separator to use here.
>>>
>>
>> Ok, thanks for your suggestion:)
>
> I fixed this one whilst merging it (faster than dropping and re-adding).
>
> Cheers,
>
> Richard
>
>
>
Thanks:)
Cheers,
Junling
prev parent reply other threads:[~2015-04-21 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 8:50 [PATCH] gmp: remove referencing paths from the build host Junling Zheng
2015-04-17 18:24 ` Andre McCurdy
2015-04-20 1:30 ` Junling Zheng
2015-04-20 15:15 ` Richard Purdie
2015-04-21 1:06 ` Junling Zheng [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=5535A290.10502@huawei.com \
--to=zhengjunling@huawei.com \
--cc=openembedded-core@lists.openembedded.org \
--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