On 28 March 2015 at 01:33, Graydon, Tracy wrote:
> +'atextappend' : '\nDISTRO_FEATURES_remove = "
> x11"\n'}},
>
FYI, _remove doesn't encourage leading whitespace.
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
http
On 28 March 2015 at 15:33, Paul Eggleton
wrote:
> When I wrote the bug I was thinking more of systems with no graphics
> at all rather than with Weston replacing X11 - not that we shouldn't be
> testing Weston though I guess.
>
I guess there's value in both. I for one certainly want to see the
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
On 28 March 2015 at 15:33, Paul Eggleton wrote:
> Hi Tracy,
>
> On Friday 27 March 2015 18:33:08 Graydon, Tracy wrote:
>> [YOCTO #6854]
>>
>> A common configuration selection is to remove x11 from
>> DISTRO_FEATURES. Add a nightly-weston.conf builset to allow us to test this
>> via the autobuilder
Pulled to master. Production post-1.8
On 28 March 2015 at 00:36, Graydon, Tracy wrote:
> [YOCTO #7519]
>
> Add the GetBitbakeVersion build step to nightly-*.conf buildsets
> in buildset_config.controller to enable toaster on autobuilder.
>
> Signed-off-by: Graydon, Tracy
> ---
> buildset-config
For some reason the menuconfig menu does not come up when I try launching it
from my Yocto installation. I am using the Toradex Yocto 1.6 system as is
described here
http://developer.toradex.com/software-resources/arm-family/linux/board-support-package/openembedded-%28core%29,
with my board set
---
recipes-devtools/spitools/spitools_git.bb | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 recipes-devtools/spitools/spitools_git.bb
diff --git a/recipes-devtools/spitools/spitools_git.bb
b/recipes-devtools/spitools/spitools_git.bb
new file mode 100644
index 000
Signed-off-by: texierp
---
recipes-devtools/spitools/spitools_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-devtools/spitools/spitools_git.bb
b/recipes-devtools/spitools/spitools_git.bb
index 287e3eb..128ad7f 100644
--- a/recipes-devtools/spitools/spitools_git.bb
+++ b/recip
On 2015-03-30 00:20, texierp wrote:
Signed-off-by: texierp
---
recipes-devtools/spitools/spitools_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-devtools/spitools/spitools_git.bb
b/recipes-devtools/spitools/spitools_git.bb
index 287e3eb..128ad7f 100644
--- a/recipes-devto
From: Alexandru Damian
The UploadToasterEventlog looks the file up in the wrong
directory, and this patch fixes that.
Signed-off-by: Alexandru DAMIAN
---
.../site-packages/autobuilder/buildsteps/UploadToasterEventlog.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a
Hi,
I'm updating to Yocto master and have been seeing that when I bitbake -c
devshell virtual/kernel I go into a work-shared tree now.
(This is all with meta-fsl-arm)
I'd normally change the kernel configuration with bitbake -c menuconfig
virtual/kernel then pull out the .config and make my chan
We are considering working on integrating Toaster with Jenkins as part of
the next Yocto Project release. Our thinking so far is collected in this
Bugzilla feature:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527
Any thoughts? Are we missing something? Are we going about it in a
completely
On 2015-03-30 01:36 PM, Alex J Lennon wrote:
Hi,
I'm updating to Yocto master and have been seeing that when I bitbake -c
devshell virtual/kernel I go into a work-shared tree now.
There was a discussion on the list about this. See the patch from
Ross:
[OE-core] [PATCH] devshell: allow the sta
On Mon, Mar 30, 2015 at 11:47 AM, Barros Pena, Belen
wrote:
> We are considering working on integrating Toaster with Jenkins as part of
> the next Yocto Project release. Our thinking so far is collected in this
> Bugzilla feature:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527
>
> Any
On 30 March 2015 at 18:36, Alex J Lennon
wrote:
> I'm updating to Yocto master and have been seeing that when I bitbake -c
> devshell virtual/kernel I go into a work-shared tree now.
>
The devshell drops you into whatever ${S} is for that recipe, which for the
kernel is ${STAGING_KERNEL_DIR} sin
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If the image gets too large, the build simply
hangs silently, without any clues or debug output to indicate why.
This patch prevents the build hanging o
Chris,
Should the hardcoded value '416080' be a variable so it can be
overridden?
- armin
On 03/30/2015 01:50 PM, Chris Hallinan wrote:
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If the
Hi Armin,
Great catching up with you last week, and thanks for looking at my
patch. I supposed it's a double edged sword. If we make it a
variable, it can be set wrong and the build hang again. OTOH, 128MB
is probably way more space than we really need to reserve, and I
supposed if someone were
Added new package data, and cleaned up whitespace.
I've also corrected some packaged data (replacement-tar from
my reading of the recipe is the tar normally found in distros).
One issue this patch exposed st I haven't had a chance to track
down is that when you attempt to get distrodata from
gcc-
On 30/03/2015 21:27, Burton, Ross wrote:
>
> On 30 March 2015 at 18:36, Alex J Lennon
> mailto:ajlen...@dynamicdevices.co.uk>>
> wrote:
>
> I'm updating to Yocto master and have been seeing that when I
> bitbake -c
> devshell virtual/kernel I go into a work-shared tree now.
>
>
> The
20 matches
Mail list logo
