From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH 00/12] 20-May-2011 Consolidated Pull
Date: Fri, 20 May 2011 16:50:53 -0700 [thread overview]
Message-ID: <4DD6FE5D.5080804@intel.com> (raw)
In-Reply-To: <4DD6FD57.5030900@linux.intel.com>
On 05/20/2011 04:46 PM, Darren Hart wrote:
>
>
> On 05/20/2011 04:45 AM, Richard Purdie wrote:
>> On Fri, 2011-05-20 at 00:06 -0700, Saul Wold wrote:
>>> This is building green on x86 and ARM.
>>>
>>> This contains updated pull requests from Khem and Dexuan. I have some
>>> non-gplv3 fixes along with a fix to the u-boot patch due to a bad checksum.
>>>
>>> I have again included the gcc 4.6 enabler for x86 and arm, the kernel
>>> updates are in place. Feel free to remove it, but I think we get a good QA
>>> pass and move forward, if not we fall back to gcc 4.5.x for RC2.
>>>
>>> Thanks for your considersation
>>
>> I've merged some of this but I do have some concerns with a few of the
>> patches:
>>
>>> Khem Raj (6):
>>> conf: Create distro overridable IMAGE varibales
>>
>> Phil had concerns about this and to be honest I agree with him. More
>> thought is needed with this, we need more of an overall plan.
>>
>>> distcc_2.18.3.bb: Fix compilation on uclibc
>>
>> I think Phil's comment on this is valid and needs to be addressed.
>>
>>> opkg_svn.bb: Install rcS.d into ${D} instead of ${IMAGE_ROOTFS}
>>
>> Should be using $D, *not* ${D}.
>
> Really? It was my understanding these are equivalent, with the {} form
> being the less ambiguous of the two for use when concatenating strings
> of variables. What am I missing?
>
Bitbake parsing occurs first and translates the ${D}, but not the $D,
see RP's comment in the main thread for this patch.
Sau!
> http://tldp.org/LDP/abs/html/parameter-substitution.html
>
> Thanks,
>
prev parent reply other threads:[~2011-05-20 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 7:06 [PATCH 00/12] 20-May-2011 Consolidated Pull Saul Wold
2011-05-20 7:06 ` [PATCH 01/12] tcmode-default: switch to gcc 4.6.0 for x86, x86-64 & arm Saul Wold
2011-05-20 7:06 ` [PATCH 02/12] modutils-cross: fix install issue Saul Wold
2011-05-20 7:06 ` [PATCH 03/12] conf: Create distro overridable IMAGE varibales Saul Wold
2011-05-20 7:06 ` [PATCH 04/12] uclibc/site_config/funcs: getloadavg is unimplemented Saul Wold
2011-05-20 7:06 ` [PATCH 05/12] nfs-utils_1.2.3.bb: Fix compile failure on uclibc Saul Wold
2011-05-20 7:06 ` [PATCH 06/12] distcc_2.18.3.bb: Fix compilation " Saul Wold
2011-05-20 7:06 ` [PATCH 07/12] opkg_svn.bb: Install rcS.d into ${D} instead of ${IMAGE_ROOTFS} Saul Wold
2011-05-20 7:06 ` [PATCH 08/12] opkg-utils: Synchronise with OE Saul Wold
2011-05-20 7:06 ` [PATCH 09/12] package-index.bb: add support for deb and rpm Saul Wold
2011-05-20 7:07 ` [PATCH 10/12] ed (GPLv2): remove --disable-silent-rules Saul Wold
2011-05-20 7:07 ` [PATCH 11/12] gettext (gplv2): add virtual/gettext to PROVIDES list Saul Wold
2011-05-20 7:07 ` [PATCH 12/12] u-boot: fix LIC_FILE_CHKSUM Saul Wold
2011-05-20 11:45 ` [PATCH 00/12] 20-May-2011 Consolidated Pull Richard Purdie
2011-05-20 23:46 ` Darren Hart
2011-05-20 23:50 ` Saul Wold [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=4DD6FE5D.5080804@intel.com \
--to=saul.wold@intel.com \
--cc=dvhart@linux.intel.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