Op 21 jun 2011, om 00:51 heeft Tom Rini het volgende geschreven:
> On 06/20/2011 01:20 PM, Darren Hart wrote:
>> I'm seeing a consistent eggdbus build failure that seems to be related
>> to the perl-native relocation. I've cleanall'd autoconf and automake,
>> native and target versions. The failu
Op 21 jun 2011, om 02:29 heeft Scott Garman het volgende geschreven:
> Packaging login.defs with base-passwd causes problems due to the
> file being included in target package installs. Instead, this
> shadow-sysroot recipe can be used by useradd.bbclass to put
> login.defs into the target sysroo
Hi Koen,
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Koen Kooi
> Sent: Friday, June 17, 2011 3:15 PM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [
On 06/21/2011 05:01 AM, Khem Raj wrote:
On Sun, Jun 19, 2011 at 6:48 PM, Robert Yang wrote:
How does this interact with rm_work?
The rm_work does not delete anything in work-shared, I think this is fine,
otherwise the source can not be shared.
it also limits the possibility of patching
login.defs is owned by shadow-utils, and doesn't belong here. The
shadow-sysroot recipe was created to handle the case this was
originally added for (useradd.bbclass support).
Signed-off-by: Scott Garman
---
.../base-passwd/base-passwd-3.5.22/login.defs | 386
.../reci
Packaging login.defs with base-passwd causes problems due to the
file being included in target package installs. Instead, this
shadow-sysroot recipe can be used by useradd.bbclass to put
login.defs into the target sysroot without disturbing packages
intended for target devices.
Signed-off-by: Scot
Hello,
This pull request moves the login.defs file previously included
with base-passwd into a more appropriate recipe, shadow-sysroot
(I'm not married to that recipe name if someone can suggest
something better).
login.defs is part of shadow-utils and the copy included with
base-passwd was conta
On 06/18/2011 11:56 AM, Paul Eggleton wrote:
FILESPATHPKG was being used to in order to bring in linux.conf and
g++.conf in this recipe, however this probably never worked since
FILESPATHPKG always has the MACHINE appended to it and these are not
machine-specific files.
FILESPATHPKG is not supp
On 06/13/2011 04:52 AM, Richard Purdie wrote:
[snip]
> Discussion
> ==
>
> I don't think option a) above is viable and the current plan implies
> we'd do b) but its extremely ugly. I'm therefore tempted to look more
> seriously at c). The bigger issues would appear to be:
>
> * It breaks
On Sun, Jun 19, 2011 at 6:48 PM, Robert Yang wrote:
>> How does this interact with rm_work?
>>
>
> The rm_work does not delete anything in work-shared, I think this is fine,
> otherwise the source can not be shared.
>
it also limits the possibility of patching the sources differently if need be.
oe-tsc minutes, 16-Jun-2011
Attending: Koen, Khem, Tom, Richard, Mark
Apologies: Stefan
Notes: Jefro
Agenda
01) choose a meeting chair
Tom
02) topics
khem: fallback source mirror for oe-core
premirrors? who maintains no-longer-upstream mirror?
kitchen-sink mirror is not a benefit for oe
On 20 jun 2011, at 21:19, "Bruce Ashfield" wrote:
> On Mon, Jun 20, 2011 at 2:44 PM, Anders Darander
> wrote:
>> I'm currently just curious, as I've played a little with 3.0-rcX in my
>> sparetime, and I've got a patch series in a local tree that at least
>> builds 3.0-rcX (and also removes s
On Mon, Jun 20, 2011 at 2:44 PM, Anders Darander wrote:
> * Bruce Ashfield [110614 17:13]:
>> Thanks for the breakdown, it definitely helps. Now that I've got some
>> 3.0-rcX items done, and recipe renaming behind me, I'll have a look
>> at these and see how best to incorporate the configs.
>
> J
* Bruce Ashfield [110614 17:13]:
> Thanks for the breakdown, it definitely helps. Now that I've got some
> 3.0-rcX items done, and recipe renaming behind me, I'll have a look
> at these and see how best to incorporate the configs.
Just curious, what 3.0-rcX items have you done? Will you submit pa
Sanity test to verify files can be fetched from the network using git, http
and https fetchers point users at a page to help get set up in the case of a
failure.
Addresses [YOCTO #933]
Signed-off-by: Joshua Lock
---
meta/classes/sanity.bbclass | 34 ++
1 files
By passing the data object to the less frequently run test harnesses
(check_sanity_tmpdir_change(), check_sanity_sstate_dir_change() and
check_sanity_version_change()) we can run tests against BitBake data here
too.
Signed-off-by: Joshua Lock
---
meta/classes/sanity.bbclass | 16 --
v2 of this change set based on feedback from Jeremy Puhlman.
Changes since v1:
* Allow checked URI's to be configurable. Note: I opted to leave the fallback
hard coded. I can certainly remove this and add them toa configuration file
somewhere if desired. If this is requested I'll probably remove t
On Mon, Jun 20, 2011 at 9:00 AM, Flanagan, Elizabeth
wrote:
> Khem,
>
> Yes, this should correct it from complaining about not having that
> license. GPL-3.0-with-GCC-exception is the correct text for
> GCCRUNTIMELIBRARYEXCEPTION and this patch changes the license over to
> that naming convention.
On Sun, 2011-06-19 at 08:03 -0700, Jeremy Puhlman wrote:
> > +test_uris= ["http://yoctoproject.org/about";,
> > +
> > "https://eula-downloads.yoctoproject.org/crownbay/crownbay-bernard-5.0.0";,
> > +
> > "git://git.yoctoproject.org/yocto-firewall-test;protocol=gi
Khem,
Yes, this should correct it from complaining about not having that
license. GPL-3.0-with-GCC-exception is the correct text for
GCCRUNTIMELIBRARYEXCEPTION and this patch changes the license over to
that naming convention. The parser chokes on portions of fields like
"GCC RUNTIME LIBRARY EXCEP
Op 20 jun 2011, om 15:55 heeft Mark Hatle het volgende geschreven:
> On 6/20/11 8:31 AM, Koen Kooi wrote:
>>
>> Op 20 jun 2011, om 15:29 heeft Phil Blundell het volgende geschreven:
>>
>>> On Mon, 2011-06-20 at 08:23 -0500, Mark Hatle wrote:
(The minor cases are primarily firmware loaded i
On Monday 20 June 2011 14:48:45 Cliff Brake wrote:
> Can you describe how the bitbake and oe-core directories are
> synchronized to content in the poky repo?
Sure. Richard can correct me on this, but my understanding is at the moment he
has a bunch of scripts that grab changes from the local clon
On 6/20/11 8:31 AM, Koen Kooi wrote:
>
> Op 20 jun 2011, om 15:29 heeft Phil Blundell het volgende geschreven:
>
>> On Mon, 2011-06-20 at 08:23 -0500, Mark Hatle wrote:
>>> (The minor cases are primarily firmware loaded into off-board cards in PCI
>>> chasis and such.. occasionally these firmware
On Sat, Jun 18, 2011 at 3:34 PM, Chris Larson wrote:
> Speaking of which, if we do that, might be a good idea to add bitbake
> itself specifically, in case any of the changes to master will impact
> the userbase.
Done, thanks.
Cliff
--
=
http://bec-systems.com
_
On Sat, Jun 18, 2011 at 1:40 PM, Paul Eggleton
wrote:
> On Saturday 18 June 2011 18:29:48 cliff.br...@gmail.com wrote:
>> meta-yocto: git://git.yoctoproject.org/poky
>>...
>>
>> Changelog for meta-yocto:
>>
>
> This clearly contains more than ju
Op 20 jun 2011, om 15:29 heeft Phil Blundell het volgende geschreven:
> On Mon, 2011-06-20 at 08:23 -0500, Mark Hatle wrote:
>> (The minor cases are primarily firmware loaded into off-board cards in PCI
>> chasis and such.. occasionally these firmware are ELF and of an architecture
>> not
>> the
On Mon, 2011-06-20 at 08:23 -0500, Mark Hatle wrote:
> (The minor cases are primarily firmware loaded into off-board cards in PCI
> chasis and such.. occasionally these firmware are ELF and of an architecture
> not
> the same as the host.. it's rare, but I have seen it before.)
Shouldn't those f
On 6/20/11 2:41 AM, Koen Kooi wrote:
> Hi,
>
> I was building qt this weekend and I noticed this one:
>
> WARNING: QA Issue: Architecture did not match (40 to 62) on
> /work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.7.3-r26.1/packages-split/qt4-embedded-tools/usr/bin/moc
> WARNING: QA Issue:
On Monday 20 June 2011 05:25:03 Dexuan Cui wrote:
> This patch eliminates the warning "not been run using the bitbake
> wrapper..." when we run bitbake-layers.
>
> Thanks Paul Eggleton for suggesting doing this in sanity.bbclass.
>
> Signed-off-by: Dexuan Cui
> ---
> meta/classes/sanity.bbclass
On Sun, Jun 19, 2011 at 22:28, Cui, Dexuan wrote:
> And I guess you're using incremental building? Does building from scratch
> work?
No; I got it when rebuilding from scratch.
into host system to it to build.
>>>
>>> Do the DEPENDS look right? Maybe this needs the class for bringing
>>>
On Mon, 2011-06-20 at 13:09 +0200, Koen Kooi wrote:
> Hi,
>
> I finally tracked down the heisenbug that was causing kernel builds to fail:
> kernel*bbclass has no DEPENDS on elfutils, but it still tries to build perf.
>
> While grepping I also stumbled accross this gem:
>
> image-swab.bbclass:P
Hi,
I finally tracked down the heisenbug that was causing kernel builds to fail:
kernel*bbclass has no DEPENDS on elfutils, but it still tries to build perf.
While grepping I also stumbled accross this gem:
image-swab.bbclass:PARALLEL_MAKE_pn-elfutils = ""
Parallel make fails only when using s
Hi Saul,
This patch will fix the issue that "native" and "nativesdk" and some
other extend recipes colud not get some information(like matainer information
or laskchecktime).
Please review it.
Thanks,
Lei
The following changes since commit 2163461ec94528ecf046a04edc5db3d2dd3a6b8
This patch will check whether the recipe is an extened recipe, if yes, some
informaiton couldn't be got, so collect those information(like maintainer
information or lastcheckversion) from non bbextended recipe.
Signed-off-by: Mei Lei
---
meta/classes/distrodata.bbclass | 46 +
Signed-off-by: Koen Kooi
---
...003-gatomic-proper-pointer-get-cast.patch.patch | 28
.../0005-glib-mkenums-interpreter.patch.patch | 25 +
meta/recipes-core/glib-2.0/glib-2.0_2.28.6.bb | 18
meta/recipes-core/glib-2.0/glib-2.0_2.2
Hi,
I was building qt this weekend and I noticed this one:
WARNING: QA Issue: Architecture did not match (40 to 62) on
/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.7.3-r26.1/packages-split/qt4-embedded-tools/usr/bin/moc
WARNING: QA Issue: Architecture did not match (40 to 62) on
/work/arm
36 matches
Mail list logo
