Hello, Yocto.
I am trynig a build of fido based yocto image, with openssl 1.0.2j for security
reason.
The openssl recipe itself builds successfully, but later in the build I see
error in jscore.
In fact, ruby is complaining that 'OPENSSL_1.0.0' is not available.
|
A release candidate build for yocto-2.1.2.rc1 is now available at:
http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.2.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-qt4 : 92a72a790a427af5f85ce86fea4fce86a72c7b58
meta-intel :
Hello, Yocto co-workers -
Our project in CHD uses the poky version Daisy, which does not include iperf3.
We've decided that we just have to have the newer version built into our
firmware to get the results we need.
One of our much better - but very busy, naturally - people took the Yocto
I know we have the remote_kick.py [1] script but i don't know if is
currently on use also this new script support list the options in
builders and specify custom ones via cmdline.
Cheers,
alimon
[1]
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/bin/remote_kick.py
On
The script supports to list avaialable builders and his options,
also can force a build if the builder is IDLE or not.
Also supports specify options via cmdline using python dictionaries
as string.
Signed-off-by: Aníbal Limón
---
bin/forcebuild.py | 183
Hi,
I am new to yocto and just started working on it. I am having issue
with meta-raspberrypi. I did inside poky
$ git checkout -b work_branch -t origin/daisy
$ git clone git://git.yoctoproject.org/meta-raspberrypi
$ source oe-init-build-env rpi-build
updated the local.conf and bblayer.conf
The format follow the one defined in the Yocto wiki:
https://wiki.yoctoproject.org/wiki/QA/xUnit_XML_Template
It is only the minimum required but it can be extended in the future.
Signed-off-by: Schuler Christian
Signed-off-by: Pascal Bach
Introduce a 4.9 bbappend for the h/w reference BSPs. Since 4.8 will
be removed, we need to have this file in place.
Signed-off-by: Bruce Ashfield
---
.../recipes-kernel/linux/linux-yocto_4.9.bbappend | 26 ++
1 file changed, 26 insertions(+)
Hi all,
4.9 has been soaking for a while now, and it is ready (as far as we know) to
be the default for the qemu* machines.
I've also introduced a 4.9 bbappend for the reference BSPs, but have not
confirmed their boot myself. The reference maintainers can follow up with
ack/nak and updates.
I
This allows to easily add additional parameters
Signed-off-by: Pascal Bach
---
main.c| 10 ++
tests/utils.c | 14 ++
utils.c | 4 ++--
utils.h | 9 -
4 files changed, 22 insertions(+), 15 deletions(-)
diff --git
2017-01-30 18:09 GMT-02:00 Daniel. :
> I'm using this little hack:
>
> do_install[depends] = "${RCONFLICTS_${PN}}:do_cleansstate"
>
DON'T DO THAT: This will make conflicting packages depend on one each other
and don't fix the problem. For the moment I'm living with the
On 1 February 2017 at 12:48, Patrick Ohly wrote:
> On Wed, 2017-02-01 at 10:38 +, colin.helliw...@ln-systems.com wrote:
> > I’ve got an odd problem with a pair of recipes:
> >
> > App ‘bar’ uses ‘libfoo’, so I’ve set a DEPENDS in bar.bb – I can see
> > this is being
Fantastic - thanks. (Thought it must have been something simple!)
-Original Message-
From: Patrick Ohly [mailto:patrick.o...@intel.com]
Sent: 01 February 2017 10:48
To: colin.helliw...@ln-systems.com
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] DEPENDS only half working
On Wed,
On Wed, 2017-02-01 at 10:38 +, colin.helliw...@ln-systems.com wrote:
> I’ve got an odd problem with a pair of recipes:
>
> App ‘bar’ uses ‘libfoo’, so I’ve set a DEPENDS in bar.bb – I can see
> this is being half picked up, because ‘bitbake bar’ shows both builds
> being started. However bar
I've got an odd problem with a pair of recipes:
App 'bar' uses 'libfoo', so I've set a DEPENDS in bar.bb - I can see this is
being half picked up, because 'bitbake bar' shows both builds being started.
However bar isn't waiting on libfoo - bar tries to compile before libfoo has
even finished
15 matches
Mail list logo