Hello Armin!
I'm trying to use the latest meta-security master in refkit. Refkit runs
yocto-compat-layer.py against its own layers, which then pulls in
meta-security as one of the dependencies. That's where I am hitting a
snag:
INFO: Detected layers:
INFO: meta-refkit: LayerType.DISTRO, /fast/wor
Hi Joe,
Is this something you or one of the other meta-selinux devs are able to help
out with or is it more of an upstream question?
Cheers,
Justin.
> On 17 Jul 2017, at 4:57 pm, Marco Ostini wrote:
>
>
> Hi All,
>
> At the moment I'm attempting to prepare a VM of morty with SELinux runnin
Dear Riko,
ffplay needs sdl as dependency, guess that's your problem
regards,
Markus
On Wed, 19 Jul 2017 09:19:24 +0800
Riko Ho wrote:
> Dear Yocto Members,
>
> I tried to compile FFplay with FFMpeg, but I can not get it ?
>
> What should I change on this code ?
>
> Here's on ffmpeg_3.3.bb
Can you submit a patch please? Thank you!
On Tue, Jul 18, 2017 at 5:15 PM Craig McQueen
wrote:
> For the python3-jinja2 package in meta-openembedded meta-python, it should
> also have a dependency on python3-numbers.
>
> I'm not sure if this dependency also applies for python-jinja2 package.
> I'
Dear Yocto Members,
I tried to compile FFplay with FFMpeg, but I can not get it ?
What should I change on this code ?
Here's on ffmpeg_3.3.bb :
===
EXTRA_OECONF = " \
--disable-stripping \
--enable-pic \
--enable-shared \
--enable-pthreads \
--enable-ffplay \
"
Thank y
For the python3-jinja2 package in meta-openembedded meta-python, it should also
have a dependency on python3-numbers.
I'm not sure if this dependency also applies for python-jinja2 package. I'm
just using the Python 3 package.
--
Craig McQueen
--
_
Hi guys,
Question for you, we were using Yocto 1.6, and I am proceeding to upgrade to
2.2, going one release at a time. Upgrade to 1.7 was with no problem, but 1.8
seems to have an issue due to missing work-shared//kernel-source
folder (aka STAGING_KERNEL_DIR or KERNEL_SRC). The folder appear
Hi Jimi,
On Tuesday, 18 July 2017 6:40:52 PM CEST Jimi Damon wrote:
> I have a recipe that I built for building jzmq, however one of the
> issues I have is with the naming of the release files from the github site.
>
> Unlike czmq which has downloads ( zip and tar.gz ) that are named
> czmq-${P
On Tue, 2017-07-18 at 09:40 -0700, Jimi Damon wrote:
> I have a recipe that I built for building jzmq, however one of the
> issues I have is with the naming of the release files from the github
> site.
>
> Unlike czmq which has downloads ( zip and tar.gz ) that are named
> czmq-${PV}.tar.gz, the d
I have a recipe that I built for building jzmq, however one of the
issues I have is with the naming of the release files from the github site.
Unlike czmq which has downloads ( zip and tar.gz ) that are named
czmq-${PV}.tar.gz, the downloads from jzmq are just called v${PV}.tar.gz.
How can I
This buildset is for support running sanity tests over a DUT like
Minnowboard for the moment only builds core-image-sato, there is a need
to make it configurable.
Also the listo of the available devices are fixed into the UI as
parameters.
[YOCTO #10604]
Signed-off-by: Aníbal Limón
---
buildse
This buildstep will copy the devices configuration from the
worker and read it, in order to get daft ip an ssh port, to
use later in RunSanityTests
[YOCTO #10604]
Signed-off-by: Aníbal Limón
Signed-off-by: Edwin Plauchu
---
config/autobuilder.conf.example| 3 +
.../autobu
This will execute daft flash cycle without reboot and prepare the dut
for sanity tests.
[YOCTO #10604]
Signed-off-by: Aníbal Limón
Signed-off-by: Edwin Plauchu
---
config/autobuilder.conf.example| 1 +
.../autobuilder/buildsteps/DaftFlash.py| 39 +++
The testimage class supports a simpleremote target specifying the
server and target ip to run tests over SSH.
The main usage of this will in conjunction with the DAFT to make
tests on real HW.
[YOCTO #10604]
Signed-off-by: Aníbal Limón
---
.../site-packages/autobuilder/buildsteps/RunSanityTest
This v3 address the following issues,
* Uses BuildImages property instead of uppercase to avoid confusion
with BB variables.
* Refactor code to get DUT configuration in lib/daft.py.
* Remove the sudo usage when executing daft flash.
Also the changes can be reviewed at,
http://git.yoctoproject.
In certain situations is need to know what images was built for
example the DAFT executes flashing over certain image.
[YOCTO #10604]
Signed-off-by: Aníbal Limón
---
lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/pyth
you need to send it to openembedde-core mailing list and use
git-send-email to submit your patch. More info on the link below
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
Leo
On Tue, 2017-07-18 at 15:43 +0200, Paulo Neves wrote:
> http://lists.openembedded.org/pipermai
On Tue, Jul 18, 2017 at 11:03 AM, wrote:
> 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 at this time, they can fill
> RECIPE_NO_UPDATE_REASON in respective recipe file to
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 at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version w
http://lists.openembedded.org/pipermail/openembedded-core/2012-September/069448.html
Workaround to avoid exit 1 status.
The reason it happens is that there are 2 missions
the state cache uses the normal fetcher to get
its's stuff and it is acceptable for it to fail.
On the other h
staging.bbclass: Refactored sysroot_stage_dir* functions.
Removed sysroot_stage_libdir because it just forwarded the
arguments to sysroot_stage_libdir with no other function.
git grep for sysroot_stage_libdir did not show any recipe
appending or overrriding sysroot_stage_libdir.
Hi everyone,
In my system, I want to build two images:
- main-image : contains the real system with applications and stuff.
- initial-flasher-image : contains a swu (swupdate file) for the first
flashing.
The images are built in this sequence: main-image > swu >
initial-flasher-image
Both images
Sorry hit send before finishing email.
So it looks like do_install and do_deploy are expecting
fitImage-${INITRAMFS_IMAGE} so is this renaming required anymore? and
if so is this a problem with the freescale kernel?
Many Thanks,
Martin.
On Tue, Jul 18, 2017 at 1:58 PM, Martin Townsend
wrote:
>
Hi,
Using Yocto 2.3 (pyro) I was trying to create a FIT image with the 4.9
linux-fslc kernel and an initramfs image. following the instructions
it failed during do_bundle_initramfs. After debugging I found that it
moves the fitImage file to fitImage.bak and then runs a second pass
and renames th
Op Mon, 17 Jul 2017 22:49:51 -0400, schreef Khem Raj:
> On Mon, Jul 17, 2017 at 3:02 PM, Ferry Toth
> wrote:
>> On edison U-Boot is 32 bit. I'm building a 64 bit kernel + rootfs.
>>
>> The only recipy that fails is U-Boot with:
>> undefined reference to `__normal___udivdi3'
>>
>>
> this means gcc
25 matches
Mail list logo
