[yocto] bbclass and recipe environnement

2019-09-11 Thread Paul Goulpié

Hello,
I am creating a bbclass of type image_types. The purpose of this class 
is to generate an archive that contains among others ipk packages that 
are created by the recipes that compose my rootfs.
My question is: how can I get the path of the IPK file for a given 
recipe from the bbclass that is being created.
More generally: how to access the environment of an application recipe 
from a bbclass.


Thanking you.

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Tuning gcc for Geode LX

2019-09-11 Thread Mauro Ziliani

Hi all.

I nee to disable all SIMD mmx sse extensions for the  GCC use to build 
the final image, containing Qt5 libraries


Now I have  tuned qtbase_git.bb by PACKAGECONFIG_CONFARGS adding the  
configure's parameters to disable MMX extensions.


But I need to disable this extensions for every package that can use MMX.


So my desire is to produce a gcc compiler that does'nt supports MMX.


I create  a machine/geode.conf with

DEFAULTTUNE="i586"

include conf/machine/include/tune-i586.inc

But I don't find how to customize the gcc/g++ parameters to disable SIMD 
extensions.



Any idea?


MZ

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-selinux][PATCH] conf/layer.conf: use BBFILES_DYNAMIC for dynamic layers

2019-09-11 Thread Joe MacDonald
[Re: [meta-selinux][PATCH] conf/layer.conf: use BBFILES_DYNAMIC for dynamic 
layers] On 19.09.11 (Wed 09:22) Yi Zhao wrote:

> 
> On 9/10/19 1:11 AM, Joe MacDonald wrote:
> > Hi Yi,
> > 
> > [[meta-selinux][PATCH] conf/layer.conf: use BBFILES_DYNAMIC for dynamic 
> > layers] On 19.09.09 (Mon 14:01) Yi Zhao wrote:
> > 
> > > From: Robert Yang 
> > > 
> > > The previous code add all BBFILE_COLLECTIONS/recipes*/*/*.bbappend to 
> > > BBFILES,
> > > which causes the parsing very slow when there are many layers, e.g., I 
> > > have 87
> > > layers:
> > > 
> > > * Before:
> > > $ rm -fr tmp-glibc/ cache; time bitbake -p
> > > real0m45.173s
> > > user0m0.560s
> > > sys 0m0.060s
> > > 
> > > * After:
> > > $ rm -fr tmp-glibc/ cache; time bitbake -p
> > > real0m25.542s
> > > user0m0.572s
> > > sys 0m0.040s
> > > 
> > > It wasted 20s which wasn't worth (The host has 128 threads, it should 
> > > cost more
> > > time on less power host), use BBFILES_DYNAMIC can fix the problem.
> > 
> > This seems like a big claim, I certainly haven't seen that on my setup:
> > 
> > * Before:
> > $ rm -fr tmp cache
> > real0m14.751s
> > user0m0.323s
> > sys 0m0.048s
> > 
> > * After:
> > $ rm -fr tmp cache ; time bitbake -p
> > real0m14.725s
> > user0m0.326s
> > sys 0m0.046s
> > 
> > but it's still a sensible change.  When I ran a test before/after
> > configuration for augeas the configuration seemed off, though.  Can you
> > confirm that with this change as is you're getting the correct
> > --with/--without and --enable/--disable and patches applied for your
> > layers?  I just want to confirm since the ~20s difference in parsing
> > seems kind of out of scale for moving essentially three bbappends around
> > and I'm wondering if there's something else siginficant in your tree we
> > want to consider.
> 
> 
> This patch is from Robert Yang. CC to him. Maybe he can give us more
> explanation.
> 
> For the augeas, the current augeas_%.bbapend doesn't work because the augeas
> recipe is in meta-oe layer but not meta-python layer. This patch moves the
> bbappend to the correct layer to fix this issue.
> 
> It works on my local:
> 
> $ cat log.do_configure
> 
> [snip]
> checking for library containing setfilecon... -lselinux
> [snip]
> checking for selinux/selinux.h... (cached) yes
> checking selinux/context.h usability... yes
> checking selinux/context.h presence... yes
> checking for selinux/context.h... yes
> [snip]

Okay, thanks.  Funny that I randomly picked the package that was broken
in multiple ways, but this looks like an improvement overall.

-J.

> 
> 
> //Yi
> 
> 
> > 
> > -J.
> > 
> > > Signed-off-by: Robert Yang 
> > > Signed-off-by: Yi Zhao 
> > > ---
> > >   conf/layer.conf   | 11 
> > > +++
> > >   .../recipes-daemons/iscsi-initiator-utils/files/initd.debian  |  0
> > >   .../iscsi-initiator-utils/iscsi-initiator-utils_%.bbappend|  0
> > >   .../iscsi-initiator-utils/iscsi-initiator-utils_selinux.inc   |  0
> > >   .../recipes-support}/augeas/augeas_%.bbappend |  0
> > >   .../recipes-containers/lxc/lxc_%.bbappend |  0
> > >   6 files changed, 7 insertions(+), 4 deletions(-)
> > >   rename {networking-layer => 
> > > dynamic-layers/networking-layer}/recipes-daemons/iscsi-initiator-utils/files/initd.debian
> > >  (100%)
> > >   rename {networking-layer => 
> > > dynamic-layers/networking-layer}/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_%.bbappend
> > >  (100%)
> > >   rename {networking-layer => 
> > > dynamic-layers/networking-layer}/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_selinux.inc
> > >  (100%)
> > >   rename {meta-python/recipes-extended/augeas => 
> > > dynamic-layers/openembedded-layer/recipes-support}/augeas/augeas_%.bbappend
> > >  (100%)
> > >   rename {virtualization-layer => 
> > > dynamic-layers/virtualization-layer}/recipes-containers/lxc/lxc_%.bbappend
> > >  (100%)
> > > 
> > > diff --git a/conf/layer.conf b/conf/layer.conf
> > > index 9dd34b1..89b9468 100644
> > > --- a/conf/layer.conf
> > > +++ b/conf/layer.conf
> > > @@ -5,10 +5,13 @@ BBPATH .= ":${LAYERDIR}"
> > >   BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
> > >   ${LAYERDIR}/recipes-*/*/*.bbappend"
> > > -# Let us add layer-specific bbappends which are only applied when that
> > > -# layer is included in our configuration
> > > -BBFILES += "${@' '.join('${LAYERDIR}/%s/recipes*/*/*.bbappend' % layer \
> > > -   for layer in BBFILE_COLLECTIONS.split())}"
> > > +BBFILES_DYNAMIC += 
> > > "openembedded-layer:${LAYERDIR}/dynamic-layers/openembedded-layer/*/*/*.bb
> > >  \
> > > +
> > > openembedded-layer:${LAYERDIR}/dynamic-layers/openembedded-layer/*/*/*.bbappend
> > >  \
> > > +
> > > networking-layer:${LAYERDIR}/dynamic-layers/networking-layer/*/*/*.bb \
> > > +
> > > networking-layer:${LAYER

[yocto] assembler error: missing immediate expression at operand 1 -- `dsb`

2019-09-11 Thread Pandey, Kamal
Hi 
I was trying to compile the rpmsg-lite library provided by NXP for my ZC102 
board. While compiling I was getting the error as follows:

| Scanning dependencies of target rpmsg-lite
| [ 10%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/rpmsg_lite.c.o
| [ 20%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/rpmsg_ns.c.o
| [ 30%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/virtio/virtqueue.c.o
| [ 40%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/porting/environment/rpmsg_env_bm.c.o
| {standard input}: Assembler messages:
| {standard input}:199: Error: missing immediate expression at operand 1 -- 
`dsb'
| {standard input}:216: Error: missing immediate expression at operand 1 -- 
`dsb'
| {standard input}:232: Error: missing immediate expression at operand 1 -- 
`dsb'
| rpmsg-lite/CMakeFiles/rpmsg-lite.dir/build.make:158: recipe for target 
'rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/porting/environment/rpmsg_env_bm.c.o'
 failed
| make[2]: *** 
[rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/porting/environment/rpmsg_env_bm.c.o]
 Error 1
| CMakeFiles/Makefile2:122: recipe for target 
'rpmsg-lite/CMakeFiles/rpmsg-lite.dir/all' failed
| make[1]: *** [rpmsg-lite/CMakeFiles/rpmsg-lite.dir/all] Error 2
| Makefile:83: recipe for target 'all' failed
| make: *** [all] Error 2
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_compile (log file is located at 
/home/iepl007/yocto_build/build_openamp/tmp/work/pdm3_zynqmp-pdm3-linux/vhip-bsp-r5-0/2018.3+gitAUTOINC+fb88b32f6e-r0/temp/log.do_compile.32551)
ERROR: Task 
(/home/iepl007/yocto_build/poky/../meta-ifm-vhip-openamp-dev/recipes-rpmsg-lite/vhip_bsp_r5_0/vhip-bsp-r5-0.bb:do_compile)
 failed with exit code '1'

While compiling mannualy without using bitbake recipe I am able to compile 
successfully.
Can someone help me resolve the issue, any pointers will be appreciated.
I am using Xilinx sdk 2018.3
Thanks & Regards
Kamal Pandey 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] source an environment file in bitbake recipe.

2019-09-11 Thread Pandey, Kamal
Hi,
Is there any way by which I can use the source command inside a bitbake recipe 
for example if I need to source some environment file before compiling.
source   doesn't seem to work 
Will  the command .   work
 
What exactly I need to inherit for source command to work
Thanks
Kamal Pandey

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] assembler error: missing immediate expression at operand 1 -- `dsb`

2019-09-11 Thread Ross Burton

On 11/09/2019 15:51, Pandey, Kamal wrote:

I was trying to compile the rpmsg-lite library provided by NXP for my ZC102 
board. While compiling I was getting the error as follows:


Try asking NXP directly.

Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-raspberrypi][ostree] build errors

2019-09-11 Thread Greg Wilson-Lindberg
I'm trying to include ostree into a raspberry pi boot2qt build based on thud.

I'm getting a warning:
WARNING: linux-raspberrypi-1_4.14.112+gitAUTOINC+6b5c4a2508-r0 
do_kernel_metadata: defconfig detected in WORKDIR. bcm2709_defconfig skipped

Which I figure that I can probably ignore, but may find I have a problem with 
it if it is missing out on my config changes.

More concerning is the following error:

ERROR: ostree-v2018.9-r0 do_unpack: gitsm: submodule unpack failed: UnpackError 
Unpack failure for URL: 
'gitsm://gitlab.gnome.org/GNOME/libglnx.git;protocol=https;name=libglnx;subpath=libglnx;bareclone=1;nobranch=1'.
 No up to date source found: clone directory not available or not up to date: 
/home/gwilson/Qt/Qt-5.13.1/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/gitlab.gnome.org.GNOME.libglnx.git;
 shallow clone not enabled

The 'gitlab.gnome.org/GNOME/libglnx' subdirectory is there, so that would imply 
that something is wrong with the initial protocol or other decorators. I also 
did a clean on ostree just to make sure there wasn't any problem with git -> 
gitsm changes.

Is there anyone with familiarity with the ostree system that could give me a 
hand on this? It is possible that I'm missing some configuration, the docs are 
not the clearest.

Thanks in advance,
Greg Wilson-Lindberg  
 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi][ostree] build errors

2019-09-11 Thread Alex Kiernan
On Thu, Sep 12, 2019 at 12:17 AM Greg Wilson-Lindberg
 wrote:
>
> I'm trying to include ostree into a raspberry pi boot2qt build based on thud.
>
> I'm getting a warning:
> WARNING: linux-raspberrypi-1_4.14.112+gitAUTOINC+6b5c4a2508-r0 
> do_kernel_metadata: defconfig detected in WORKDIR. bcm2709_defconfig skipped
>
> Which I figure that I can probably ignore, but may find I have a problem with 
> it if it is missing out on my config changes.
>
> More concerning is the following error:
>
> ERROR: ostree-v2018.9-r0 do_unpack: gitsm: submodule unpack failed: 
> UnpackError Unpack failure for URL: 
> 'gitsm://gitlab.gnome.org/GNOME/libglnx.git;protocol=https;name=libglnx;subpath=libglnx;bareclone=1;nobranch=1'.
>  No up to date source found: clone directory not available or not up to date: 
> /home/gwilson/Qt/Qt-5.13.1/Yocto-build-RPi3/build-raspberrypi3/../downloads/git2/gitlab.gnome.org.GNOME.libglnx.git;
>  shallow clone not enabled
>
> The 'gitlab.gnome.org/GNOME/libglnx' subdirectory is there, so that would 
> imply that something is wrong with the initial protocol or other decorators. 
> I also did a clean on ostree just to make sure there wasn't any problem with 
> git -> gitsm changes.
>
> Is there anyone with familiarity with the ostree system that could give me a 
> hand on this? It is possible that I'm missing some configuration, the docs 
> are not the clearest.
>

My immediate thought was add:

PREMIRRORS = ""

to your ostree recipe - there's an old copy of the source sitting in
the yocto mirrors and the gitsm fetcher doesn't update the submodules
correctly, but looking at the error, I'm not sure if that's actually
your problem.

I'm a couple of upstream patches away from an ostree recipe that's I
think should be in a fit state to go into meta-oe:

https://github.com/akiernan/meta-ostree-core/blob/master/recipes-ostree/ostree/ostree.inc

-- 
Alex Kiernan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto