Bruce Ashfield wrote:
> 2011/1/10 Cui, Dexuan :
>> hmmm, looks this commit was not tested?
>
> It was definitely tested. Built for every board. Feel free to revert
> as required.
Hi Bruce,
I'm building poky-image-minimal on today's latest poky master 4b055ed and got
the following failure.
>> Wit
2011/1/10 Cui, Dexuan :
> hmmm, looks this commit was not tested?
It was definitely tested. Built for every board. Feel free to revert as
required.
Bruce
>
> With poky.git's latest 4b055ed, "bitbake kern-tools-native -c fetch" fails
> because in http://git.pokylinux.org/cgit/cgit.cgi/wr-kernel
Hi Richard,
When testing the machine specific sysroot patchset for atom-pc and emenlow
machines, it exposed a libtool issue that, after the built of "Machine A", and
then try to build "Machine B" of the same architecture, those "-L" paths
generated by libtool still points to the "Machine A" sys
hmmm, looks this commit was not tested?
With poky.git's latest 4b055ed, "bitbake kern-tools-native -c fetch" fails
because in http://git.pokylinux.org/cgit/cgit.cgi/wr-kernel-tools/, the latest
commit is still a494ddaf1c9151af8af8050e8427c9958440ec4c.
Thanks,
-- Dexuan
-Original Message-
Hi Beth,
The following are the symlink names after a local build of qemu images which
are missing from the autobuilder:
Kernels:
bzImage-qemux86.bin
bzImage-qemux86-64.bin
zImage-qemuarm.bin
zImage-qemuppc.bin
vmlinux-qemumips.bin
rootfs:
poky-image-sdk-qemux86-64.tar.bz2/ext3
poky-image-sdk-
The answer to this, is that the nightly-*-incrementals were copying
their output to the webserver nightly (which updated CURRENT). As there
was a change to the incrementals on Friday that broke kernel deploy, the
kernel didn't get copied. That is now fixed.
You should look at: http://autobuilder.p
Hi,
I searched in meta/* but did not found a ntp client like.
busybox have one but yocto don't compiles it, by default.
I can use a busybox.append or change busybox recipe.
In this cases, what is the best to do?
Thanks
--
---
João Henri
On Mon, 2011-01-10 at 12:30 -0500, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrid
Fixes [BUGID: 620]
Update the SRCREVs to include the full 2.6.37 release plus the
forward port of the alternate RPC port patch. With this fix,
we can complete usermode NFS booting of all the qemu* targets.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc |
Update the SRCREV to pickup changes to update the use of
WRS_* to be K* to provide more generic names for the
platform/board/kernel configuration options.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc |4 ++--
1 files changed, 2 insertions(+), 2 deletio
Updating to reflect the changes from Darren Hart:
[
linux-yocto-2.6.37: Add debugfs and ftrace features to standard ktype
meta-data
ftrace provides low impact tracing facilities and should be made
available on the main kernel - as opposed to a debug or tracing
kernel which often
Fixes [BUGID #581]
The initial routerstation pro BSP went out with with command line
overrides enabled. We'd need to be able to set the command line
from Redbot, so we should disable the forcing of the built in
variant.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revi
configme used to be able to calculate the output/build directory
when branches were always -. Branch names
can now be widely different and to avoid embedding complexity
in the scripts it is easier to just pass ${B} from the build system
down to the scripts.
Signed-off-by: Bruce Ashfield
---
meta
It looks like some of my last pull request didn't make it
to master, so I've repeated it here. Patches 4/5 have already
been sent:
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
The remaining three changes are new and are:
- A merge from Dar
I see that and I think I know what is going on. I should have a fix for
this today.
-b
On 01/09/2011 05:25 PM, Xu, Jiajun wrote:
>> I've made a few changes to the autobuilder that people should know about.
>> Currently, we've been utilizing the milestone builders to split the
>> nightly to both t
Hi, Jiajun
since sanity test works fine now, just want to know if there's any possible for
adding some test cases for SDK side.
1. We want to know whether unfs qemu could work fine. Since we only support
booting unfs qemu in with our SDK plugins (Eclipse, ANJUTA)
2. When our SDK installer is r
16 matches
Mail list logo
