I wanted to give people a heads up about the addition of a few more
targets to the nightly build and how they'll effect the nightly (and our
overall efficency).
This bug asks for the addition of a few targets:
arm: beagleboard: poky-image-sato, poky-image-minimal, poky-image-sdk
Lu, Lianhao wrote:
Richard Purdie wrote on 2010-12-08:
Hi Lianhao,
On Tue, 2010-12-07 at 00:02 -0800, Lu, Lianhao wrote:
I'm wondering whether-sysroot is enough for our current design
that the rootfs used by toolchain can be copied by the user to
various locations? I just bumped into a
Richard,
Consider these patches for merging. I've been building and working
with these for 2 weeks now, and while they aren't perfect, they
work and we need more eyes on 2.6.37.
What we get is the following:
- factoring of the code into some reusable routines in the form
of a linux-yocto
Modify linux-libc-headers-yocto to use the common linux-yocto
routines, so headers exported to userspace will track the
branches in the yocto kernel git repository.
This commit also switches supported boards to prefer the
yocto libc headers.
Signed-off-by: Bruce Ashfield
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
is broken into three parts:
- meta/classes/kernel-yocto.bbclass: contains common routines
On Tue, 2010-12-07 at 19:15 -0800, Kamble, Nitin A wrote:
I am getting following bitbake error. I also tried passing –D
option
to bitbake, but I did not find anything useful. Also bellow is the
change which is causing this error.
I don’t see anything oblivious here. As I understand
On 12/08/2010 04:49 AM, Richard Purdie wrote:
Hi,
We're in a position where we have people wanting to extend Poky but
wondering exactly how to add their own layer and make Poky useful for
their specific use cases.
This is a topic I want to work with the OE community on and have
discussion
On Wed, 2010-12-08 at 08:29 -0800, Kamble, Nitin A wrote:
On Tue, 2010-12-07 at 19:15 -0800, Kamble, Nitin A wrote:
I am getting following bitbake error. I also tried passing –D
option
to bitbake, but I did not find anything useful. Also bellow is the
change which is causing this
On 12/08/2010 12:32 AM, Xu, Jiajun wrote:
I wanted to give people a heads up about the addition of a few more
targets to the nightly build and how they'll effect the nightly (and our
overall efficency).
This bug asks for the addition of a few targets:
arm: beagleboard: poky-image-sato,
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
Richard,
FYI: Darren pointed out that these should go to poky@
as well, so any follow ups will go to both lists. Sorry
about the initial miss!
Cheers,
Bruce
Consider these patches for merging. I've been building and working
with these for 2
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
There may be a minor problem with this, stay tuned.
I just had a strange failure when I built the 2.6.37
On 10-12-08 03:20 PM, Bruce Ashfield wrote:
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
There may be a minor problem with this, stay tuned.
I just had
Thanks Richard for the clarification. So what would be possible
solution for this circular dependency issue? I can check if we can
get
the latest gnu-config via cvs. Any other or better solution?
Is there a release tarball we can use? If not, we might end up hosting
a
release
Hi, Jessica
FYI.
TCF terminal/shell java code part is now in upstream.
Thanks Regards,
criping
-Original Message-
From: bugzilla-dae...@eclipse.org [mailto:bugzilla-dae...@eclipse.org]
Sent: Wednesday, December 08, 2010 11:54 PM
To: Ke, Liping
Subject: [Bug 246987] [tcf] Would be
14 matches
Mail list logo
