Openembedded Core Discussions
 help / color / mirror / Atom feed
From: jhuang0 <jackie.huang@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [PATCH 1/1] apr-util: fix the rules.mk with path to sysroot instead of the workdir of apr
Date: Tue, 21 Aug 2012 11:14:39 +0800	[thread overview]
Message-ID: <5032FD1F.7030805@windriver.com> (raw)
In-Reply-To: <20120817121307.GG3625@jama.jama.net>



On 8/17/2012 8:13 PM, Martin Jansa wrote:
> On Fri, Aug 17, 2012 at 11:11:43AM +0800, jackie.huang@windriver.com wrote:
>> From: Jackie Huang <jackie.huang@windriver.com>
>>
>> The copying for rules.mk was happened in do_configure_prepend, but it will be
>> replaced by the one generated by configure, in which APR_MKEXPORT points to
>> the workdir of apr and cause compile filure when the workdir of apr is removed.
>> So change the copying in _prepend to _append.
>>
>> [YOCTO #2947]
>>
>> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
>> ---
>>   meta/recipes-support/apr/apr-util_1.4.1.bb |    6 ++++--
>>   1 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-support/apr/apr-util_1.4.1.bb b/meta/recipes-support/apr/apr-util_1.4.1.bb
>> index deb608f..0516bc4 100644
>> --- a/meta/recipes-support/apr/apr-util_1.4.1.bb
>> +++ b/meta/recipes-support/apr/apr-util_1.4.1.bb
>> @@ -32,8 +32,10 @@ inherit autotools lib_package binconfig
>>
>>   OE_BINCONFIG_EXTRA_MANGLE = " -e 's:location=source:location=installed:'"
>>
>> -do_configure_prepend() {
>> -	cp ${STAGING_DATADIR}/apr/apr_rules.mk ${S}/build/rules.mk
>> +do_configure_append() {
>> +	if [ "${PN}" == "${BPN}" ]; then
>> +		cp ${STAGING_DATADIR}/apr/apr_rules.mk ${S}/build/rules.mk
>> +	fi
>>   }
>>   do_configure_prepend_virtclass-native() {
>>   	cp ${STAGING_DATADIR_NATIVE}/apr/apr_rules.mk ${S}/build/rules.mk
>
> Why is it different then native case above?
>

The bug didn't happen in native case since the related paths in rules.mk 
generated by configure for apr-util-native were pointed to the correct 
dirs in sysroot, so this fix is only applied for BPN.

And I checked that what makes this difference is the different 
'location' in apr-1-config of BPN and native one:

  $ diff intel-atom/usr/bin/crossscripts/apr-1-config 
x86_64-linux/usr/bin/apr-1-config | tail -n 4
49c49
< location=source
---
 > location=installed


Thanks,
Jackie

> Shouldn't be the same fix prepend/append applied for native case too and
> then "${PN}" == "${BPN}" won't be needed?
>
> Cheers,
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

-- 
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745



  reply	other threads:[~2012-08-21  3:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  3:11 [PATCH 0/1] apr-util: fix the rules.mk with path to sysroot instead of the workdir of apr jackie.huang
2012-08-17  3:11 ` [PATCH 1/1] " jackie.huang
2012-08-17 12:13   ` Martin Jansa
2012-08-21  3:14     ` jhuang0 [this message]
2012-08-21 15:33 ` [PATCH 0/1] " Saul Wold

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=5032FD1F.7030805@windriver.com \
    --to=jackie.huang@windriver.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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