Hej
Some software can be only tested on the final system. For that it would be
usefull to start with a debug version of that app and change it later to
release.
In my case I have a software which do logging. The amount of the logs
depends on type of the build (Release skips all debug messages)
On Wed, 17 Aug 2016, Gary Thomas wrote:
> On 2016-08-16 18:38, Robert P. J. Day wrote:
> > On Tue, 16 Aug 2016, Khem Raj wrote:
> >
> > > > On Aug 16, 2016, at 8:37 AM, Robert P. J. Day
> > > > wrote:
> > > >
> > > > On Tue, 16 Aug 2016, Patrick Doyle wrote:
> > > >
> > > > > As I am playing with
I've just had to upgrade from Mono 4.2.x to Mono 4.4.x, to get a fix for SMTP
SSL/TLS.
I'm using the mono-libs-4.5 package. I see that the size of it has increased
quite a lot (several MB) due to the upgrade. It looks as though it's now
putting a bunch of files in /usr/lib/mono/4.5-api in addit
On 2016-08-16 18:38, Robert P. J. Day wrote:
On Tue, 16 Aug 2016, Khem Raj wrote:
On Aug 16, 2016, at 8:37 AM, Robert P. J. Day wrote:
On Tue, 16 Aug 2016, Patrick Doyle wrote:
As I am playing with several different Yocto/OE projects, I thought
it would be nice to set up a global downloads
Fixes taskhash mismatch e.g.
ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch
78b2e0830a66052318e5e7eba193 versus 4b9bbe5dba1b48cf5cb5ad365d991de9 for
/a/builder/home/kraj/work/oe/openembedded-core/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
ERROR:
Hello Joshua,
We did not want bins like setfacl,setcap,chsmack etc.. to be kept on target .
- wanted to understand "how does this postscript gets copied to target and at
which path"?
- I will have multiple recipe that will have this postscript to set respective
packages bin's "acl" permission
Hi,
Is there a way to disable recipes to be excluded in eSDK?
I am facing issues while extracting an SDK, which complains about kernel
fragments are left over in setscene
Thanks
Manju
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yo
> On Aug 16, 2016, at 4:12 PM, Jianxun Zhang
> wrote:
>
> Runtime test script failed on T100TA (32 bit) machine because
> read_file() function in rmc.c gets a wrong value of st_size from
> the buffer returned by stat(). We include rmc header files prior
> to the rest of standard header files in
Use a common script to check for a running vnc server, and if not running
cleanup dangling lock files and restart the server.
[YOCTO #8210]
Signed-off-by: Bill Randle
---
bin/checkvnc | 10 ++
.../site-packages/autobuilder/buildsteps/Run
When used with corresponding oe-core patch, this will enable the use
of kvm when running qemux86* images on a x86* host that supports kvm.
On the same build machine, for an x86_64 testimage run, the with and
without times are:
without kvm:
core-image-sato-1.0-r0 do_testimage: Ran 43 tests in
Signed-off-by: Jianxun Zhang
---
src/rmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/rmc.c b/src/rmc.c
index 6cf584e..7f63c59 100644
--- a/src/rmc.c
+++ b/src/rmc.c
@@ -112,7 +112,7 @@ static int read_file(const char *pathname, char **data,
size_t* len) {
whi
Runtime test script failed on T100TA (32 bit) machine because
read_file() function in rmc.c gets a wrong value of st_size from
the buffer returned by stat(). We include rmc header files prior
to the rest of standard header files in rmc.c, so standard data
subsequently defined could be affected by "
Two test scripts cover basic functionality in both build and
runtime with some sample data of three boards.
Signed-off-by: Jianxun Zhang
---
This is the first patch to rmc project since it was published in YP.
After consulting some people, we choose yocto mailing list for rmc
patch review.
Thank
On Tue, Aug 16, 2016 at 4:24 PM, Peter Kjellerstedt
wrote:
> You seem to be using an old version of Poky.
I am using the version of poky distributed with the board. In this
case, the board is the Edison board, and the manufacturer is Intel. I
guess I was assuming that the Edison would have been
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Patrick Doyle
> Sent: den 16 augusti 2016 17:13
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] How to maintain a global DL_DIR?
>
> Oh this is ugly...
> I tried setting
On Tue, 2016-08-16 at 11:55 +, Kumar, Shrawan wrote:
> Thanks Joshua,
>
> "postinst" works!! I could see the attributes set under
> "poky/build_qemux86/tmp/work/qemux86-poky-linux/core-image-
> minimal/1.0-r0/rootfs/".
>
> However, I still could not see the attributes after booting qemu. I
Hi All
I have put together recipe upgrade for upcoming gcc 6.2 release now that it
entered RC phase. With gcc 6.2 the recipes are using tarballs instead of git
fetcher as promised :)
Please help testing it out in your setups and report any issues you see.
The commit you need to cherry-pick for
The non-upstream URIs were accidentally still pointing to Mars data.
Signed-off-by: Tim Orling
---
scripts/setup.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/setup.sh b/scripts/setup.sh
index 30f4463..75310ab 100755
--- a/scripts/setup.sh
+++ b/scripts/setup
I have created a recipe for to add the Azure libraries to a Yocto image. I see
the libraries are included in the the Azure rpm file and the .so’s and include
files in the dev rpm. I second recipe to test being able to link to the
libraries also builds and links correctly. However, in the do_r
On Tue, 16 Aug 2016, Khem Raj wrote:
> > On Aug 16, 2016, at 8:37 AM, Robert P. J. Day wrote:
> >
> > On Tue, 16 Aug 2016, Patrick Doyle wrote:
> >
> >> As I am playing with several different Yocto/OE projects, I thought
> >> it would be nice to set up a global downloads directory.
> >>
> >> Also
> On Aug 16, 2016, at 8:37 AM, Robert P. J. Day wrote:
>
> On Tue, 16 Aug 2016, Patrick Doyle wrote:
>
>> As I am playing with several different Yocto/OE projects, I thought
>> it would be nice to set up a global downloads directory.
>>
>> Also, being a somewhat forgetful sort, I thought it wo
On Tue, 16 Aug 2016, Patrick Doyle wrote:
> As I am playing with several different Yocto/OE projects, I thought
> it would be nice to set up a global downloads directory.
>
> Also, being a somewhat forgetful sort, I thought it would be nice if
> I could set DL_DIR in my .bashrc and not have to rem
Still going to the wrong list use: meta-virtualizat...@yoctoproject.org.
On 2016-08-15 11:21 PM, kai.k...@windriver.com wrote:
From: Kai Kang
Backport patch to fix CVE-2016-5008 from:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=f32441c
I typically prefer uprevs to backports for these
Oh this is ugly...
I tried setting BB_ENV_EXTRAWHITE to DL_DIR in my .bashrc, but found
that BB_ENV_EXTRAWHITE gets overwritten by oe-buildenv-internal as I
mentioned previously.
I tried setting BB_ENV_WHITELIST to DL_DIR in my .bashrc and found
that bitbake just stopped working.
After rereading
As I am playing with several different Yocto/OE projects, I thought it
would be nice to set up a global downloads directory.
Also, being a somewhat forgetful sort, I thought it would be nice if I
could set DL_DIR in my .bashrc and not have to remember to edit
conf/local.conf each time I follow the
Thanks Joshua,
"postinst" works!! I could see the attributes set under
"poky/build_qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/".
However, I still could not see the attributes after booting qemu. It seems
during rootfs.ext4 (mkfs.ext4 command )creation when "create_i
From: Kai Kang
qemu is not compatible with mips64, so remove 'qemu' which causes
libvirt depends on package qemu from PACKAGECONFIG for mips64.
Signed-off-by: Kai Kang
---
recipes-extended/libvirt/libvirt_1.3.5.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/recipes-extended/libvirt/
27 matches
Mail list logo
