From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: [PATCH 6/7] package_rpm: use target vendor information
Date: Fri, 6 May 2011 13:02:36 -0500 [thread overview]
Message-ID: <4DC437BC.4070500@windriver.com> (raw)
In-Reply-To: <4DC42DAF.3080605@linux.intel.com>
On 5/6/11 12:19 PM, Darren Hart wrote:
> Hi Adrian,
With the issue fixed below, this looks like a good change to me.
--Mark
> One issue below:
>
> On 05/05/2011 12:11 PM, Adrian Alonso wrote:
>> * Instead of hardcoding target vendor string "-poky"
>> use TARGET_VENDOR information in case of using external
>> toolchains
>>
>> Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
>> ---
>> meta/classes/package_rpm.bbclass | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/classes/package_rpm.bbclass b/meta/classes/package_rpm.bbclass
>> index 70170d1..1cf9f79 100644
>> --- a/meta/classes/package_rpm.bbclass
>> +++ b/meta/classes/package_rpm.bbclass
>> @@ -761,13 +761,14 @@ python do_package_rpm () {
>> # Setup the rpmbuild arguments...
>> rpmbuild = bb.data.getVar('RPMBUILD', d, True)
>> targetsys = bb.data.getVar('TARGET_SYS', d, True)
>> + targetvendor = bb.data.getVar('TARGET_VENDOR', d, True)
>> pkgwritedir = bb.data.expand('${PKGWRITEDIRRPM}/${PACKAGE_ARCH}', d)
>> pkgarch = bb.data.expand('${PACKAGE_ARCH}', d)
>> bb.mkdirhier(pkgwritedir)
>> os.chmod(pkgwritedir, 0755)
>>
>> cmd = rpmbuild
>> - cmd = cmd + " --nodeps --short-circuit --target " + pkgarch + "-poky-linux-gnu --buildroot " + pkgd
>> + cmd = cmd + " --nodeps --short-circuit --target " + pkgarch + targetvendor + "-linux-gnu --buildroot " + pkgd
>
> You need:
> + "-" + targetvendor
>
> otherwise you'll merge pkgarch and targetvendor together without a delimiter.
> Better yet, just format the string in one go and reduce the potential for error:
>
> cmd = "%s --nodeps --short-circuit --target %s-%s-linux-gnu --buildroot %s" % \
> (rpmbuild, pkgarch, targetvendor, pkgd)
>
next prev parent reply other threads:[~2011-05-06 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 19:10 [PATCH 0/7] Microblaze target arch support Adrian Alonso
2011-05-05 19:10 ` [PATCH 1/7] insane: add micrblaze target info Adrian Alonso
2011-05-08 6:14 ` Khem Raj
2011-05-09 14:24 ` Adrian Alonso
2011-05-05 19:10 ` [PATCH 2/7] kernel-arch: add microblaze to valid archs Adrian Alonso
2011-05-05 19:10 ` [PATCH 3/7] siteinfo: add microblaze target info Adrian Alonso
2011-05-05 19:11 ` [PATCH 4/7] linux-libc-headers: add microblaze ARCH definition Adrian Alonso
2011-05-05 19:11 ` [PATCH 5/7] image-mklibs: add microblaze arch support Adrian Alonso
2011-05-05 19:11 ` [PATCH 6/7] package_rpm: use target vendor information Adrian Alonso
2011-05-06 17:19 ` Darren Hart
[not found] ` <BANLkTi=xgBnjob=1U7yaPFyT-y075odAvA@mail.gmail.com>
2011-05-06 17:58 ` Adrian Alonso
2011-05-06 18:48 ` Darren Hart
2011-05-06 18:02 ` Mark Hatle [this message]
2011-05-05 19:11 ` [PATCH 7/7] readline: update version Adrian Alonso
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=4DC437BC.4070500@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.