Re: [yocto] scipy recipe

[Manjukumar Harthikote Matha]

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On Behalf Of Matthias Schöpfer
> Sent: Friday, March 23, 2018 3:08 AM
> To: Peter Balazovic ; Yocto-mailing-list
> 
> Subject: Re: [yocto] scipy recipe
> 
> Hi Peter,
> 
> I managed to get scipy to cross compile, since I was in a hurry, and have no 
> deeper
> understanding of python / distutils / setuptools, it turned out to be an ugly 
> hack (but
> obviously I was not the first one to do ugly things there ;) )
> 
> Maybe you have had some progress as well, and we can figure out a nicer 
> solution.
> 
> See the attached files, involving openblas, a bbappend for python-numpy and
> python-scipy.
> 

Thanks Matthias, will try this out

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

Re: [yocto] How to add a module to python-native

[Burton, Ross]

You'll need to run $bindir_native/python/python, we isolate the native
Python from the host python so you need to invoke the native one
explicitly.  In a recipe you can just do inherit pythonnative, but
don't do that in a class which every recipe is inheriting!

Ross

On 26 March 2018 at 21:01, Ulf Samuelsson  wrote:
> Need some advice on how to extend python-native with a python-2.7 module.
>
> I am planning to upload the result of cve-check to our JIRA server.
> I wrote a python application which reads the CVE manifest,
> downloads the contents of a JIRA project and if a CVE issue
> is not present in the database, it will create new issues.
>
> The python application is using the python-restkit module, which has all the
> functionality I need, so I can call 

[yocto] how to add pulseaudio

[Sherif Omran]

hello

i am trying to add pulse audio to an image but i don't get pulse audio
being installed in the image

I am using the following
DISTRO_FEATURES_append += " ext2 pam usbhost ${DISTRO_FEATURES_LIBC}
pulseaudio pulseaudio-module-dbus-protocol pulseaudio-module-bluetooth"
IMAGE_INSTALL_append += " python dbus gconf glib-2.0"

what am i doing wrong?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to add a module to python-native

[Ulf Samuelsson]

Need some advice on how to extend python-native with a python-2.7 module.

I am planning to upload the result of cve-check to our JIRA server.
I wrote a python application which reads the CVE manifest,
downloads the contents of a JIRA project and if a CVE issue
is not present in the database, it will create new issues.

The python application is using the python-restkit module, which has all 
the functionality I need, so I can call 

Re: [yocto] U-Boot networking broken in Rocko

[Robert Berger]

On 2018-03-26 19:51, akuster808 wrote:

I found 
that this has already been fixed in U-Boot with the commit below.  I 
think it has something to do with the way GCC 7.1 onwards is now 
handling memory alignment.  


I also saw something similar and by upgrading to U-boot 2018.03 the 
problem went away as well.


Regards,

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

Re: [yocto] [matchbox-wm][PATCH] configure.ac: add lib math for composite enabled builds

[Burton, Ross]

On 26 March 2018 at 11:26, Awais Belal  wrote:
> The composite enabled builds require lib math to be
> present on the linker command line otherwise we get
> ld: composite-engine.o: undefined reference to symbol 'exp@@GLIBC_2.2.5'
> during compilation.
>
> Signed-off-by: Awais Belal 
> ---
>  configure.ac | 6 --
>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index dce82cc..1bc113f 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -246,9 +246,11 @@ fi
>  dnl -- Composite ---
>
>  if test x$enable_composite != xno; then
> -  PKG_CHECK_MODULES(COMPO, xcomposite xfixes xdamage xrender, ,
> +  PKG_CHECK_MODULES(COMPO, xcomposite xfixes xdamage xrender, 
> have_compo_deps=yes,
>AC_MSG_ERROR([*** Required Composite Librays not 
> installed ***]))
> -
> +  if test x$have_compo_deps = xyes; then
> +COMPO_LIBS="$COMPO_LIBS -lm"
> +  fi

There's no way that test can fail as if the packages are not found,
configure aborts.  Just do the assignment without the test.

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

[yocto] Yocto Project Status WW13’18

[Stephano Cetola]

Current Dev Position: YP 2.5 M3 final close out.
Next Deadline: YP 2.5 M4 stabilization is 4/2/18

SWAT lead is currently Ross.
SWAT team rotation: Ross -> Juro on March 30, 2018
SWAT team rotation: Juro -> Paul on April 6, 2018
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:
· YP 2.5 M3 rc1 was built and went into QA. This release was built on
with the ‘new’ autobuilder codebase. Some issues were found with
artefact publication but nothing to block the rc1 as yet.
· We are still blocked with morty on the glibc 2.27 and the sdk locale
issues
· Code has been added to uninative to ensure the glibc corruption that
occurred with the newer glibc cannot happen again.
· We have found a new issue where fedora 27’s version of coreutils is
using syscall() to call a syscall directly and hence corrupting
permissions of some files from pseudo’s perspective. We’re currently
discussing this with upstream as its looking problematic to fix and we’d
much prefer they use the glibc wrappers.
· We have a fix for the qemuarm64 hangs during early boot, thanks to
everyone who’s helped fix that, its much appreciated and will help our
automated tests.
· A significant win in opkg compression speed was found (thanks Ross!)

Planned upcoming dot releases:
YP 2.3.4 (Pyro) will be built after 2.5 M3
YP 2.2.4 (Morty) will be built after 2.5 M3 once the glibc 2.27 issue is
fixed
YP 2.4.3 (Rocko) is planned for post YP 2.5.

Key YP 2.5 Dates are:
YP 2.5 M3 is in QA.  See status above.
YP 2.5 M3 was scheduled for release 3/2/18
YP 2.5 M4 cut off of 4/2/18
YP 2.5 M4 release of 4/27/18

Tracking Metrics:
  WDD 2673 (last week 2673)
(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]

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

Re: [yocto] U-Boot networking broken in Rocko

[akuster808]

On 03/26/2018 08:47 AM, Martin Townsend wrote:
> Hi,
>
> I've discovered that U-Boot in Rocko for several builds that I
> maintain is broken when performing various network related operations
> like tftp, dhcp and ping. You get a data abort and it resets.  I found
> that this has already been fixed in U-Boot with the commit below.  I
> think it has something to do with the way GCC 7.1 onwards is now
> handling memory alignment.  Anyway the problems have gone away when I
> apply this patch and was wondering if it should be included in the
> U-Boot recipes in Rocko, or is no-one else seeing this problem?

please send a patch to openembedded-c...@lists.openembedded.org

with rocko called on in the beginning of subject line

thanks,
Armin
>
> Many Thanks,
> Martin.
>
> commit 704f3acfcf55343043bbed01c5fb0a0094a68e8a
> Author: Denis Pynkin  >
> Date:   Fri Jul 21 19:28:42 2017 +0300
>
>     net: Use packed structures for networking
>     
>     PXE boot is broken with GCC 7.1 due option '-fstore-merging' enabled
>     by default for '-O2':
>     
>     BOOTP broadcast 1
>     data abort
>     pc : [<8ff8bb30>]          lr : [<4f1f>]
>     reloc pc : [<17832b30>]    lr : [<878abf1f>]
>     sp : 8f558bc0  ip :      fp : 8ffef5a4
>     r10: 8ffed248  r9 : 8f558ee0     r8 : 8ffef594
>     r7 : 000e  r6 : 8ffed700     r5 :   r4 : 8ffed74e
>     r3 : 00060101  r2 : 8ffed230     r1 : 8ffed706  r0 : 0ddd
>     Flags: nzcv  IRQs off  FIQs off  Mode SVC_32
>     Resetting CPU ...
>     
>     Core reason is usage of structures for network headers without packed
>     attribute.
>     
>     Reviewed-by: Yauheni Kaliuta  >
>     Signed-off-by: Denis Pynkin  >
>     Acked-by: Joe Hershberger  >
>
>
>

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

[yocto] U-Boot networking broken in Rocko

[Martin Townsend]

Hi,

I've discovered that U-Boot in Rocko for several builds that I maintain is
broken when performing various network related operations like tftp, dhcp
and ping. You get a data abort and it resets.  I found that this has
already been fixed in U-Boot with the commit below.  I think it has
something to do with the way GCC 7.1 onwards is now handling memory
alignment.  Anyway the problems have gone away when I apply this patch and
was wondering if it should be included in the U-Boot recipes in Rocko, or
is no-one else seeing this problem?

Many Thanks,
Martin.

commit 704f3acfcf55343043bbed01c5fb0a0094a68e8a
Author: Denis Pynkin 
Date:   Fri Jul 21 19:28:42 2017 +0300

net: Use packed structures for networking

PXE boot is broken with GCC 7.1 due option '-fstore-merging' enabled
by default for '-O2':

BOOTP broadcast 1
data abort
pc : [<8ff8bb30>]  lr : [<4f1f>]
reloc pc : [<17832b30>]lr : [<878abf1f>]
sp : 8f558bc0  ip :  fp : 8ffef5a4
r10: 8ffed248  r9 : 8f558ee0 r8 : 8ffef594
r7 : 000e  r6 : 8ffed700 r5 :   r4 : 8ffed74e
r3 : 00060101  r2 : 8ffed230 r1 : 8ffed706  r0 : 0ddd
Flags: nzcv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

Core reason is usage of structures for network headers without packed
attribute.

Reviewed-by: Yauheni Kaliuta 
Signed-off-by: Denis Pynkin 
Acked-by: Joe Hershberger 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][PATCH 2/2] requirements.txt: use the most recent Django 1.8 version

[akuster808]

Paul,

Have you seen this ?

https://www.djangoproject.com/download/#supported-versions

1.8 will EOL this April


- armin


On 03/25/2018 12:31 PM, Paul Eggleton wrote:
> Use <1.9 to always get the most recent 1.8 point release.
>
> Signed-off-by: Paul Eggleton 
> ---
>  requirements.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/requirements.txt b/requirements.txt
> index 58100a9..30573a6 100644
> --- a/requirements.txt
> +++ b/requirements.txt
> @@ -3,7 +3,7 @@ anyjson==0.3.3
>  billiard==3.5.0.3
>  celery==4.1.0
>  confusable-homoglyphs==2.0.2
> -Django==1.8.18
> +Django<1.9
>  django-cors-headers==1.1.0
>  django-nvd3==0.9.7
>  django-ranged-response==0.2.0

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

[yocto] chrpath error: Building SDK fails after porting to Rocko

[Martin Townsend]

Hi,

I've just ported my build to Rocko but I now can't build the SDK, the
offending package is u-boot-tools which I have based on u-boot-mkimage
(which also fails with the same error message).  Does anyone have any idea
on how to debug/fix this?

Build Configuration:
BB_VERSION   = "1.36.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal-4.8"
TARGET_SYS   = "arm-bia-linux-gnueabi"
MACHINE  = "varsomam43"
DISTRO   = "bia"
DISTRO_VERSION   = "20180207-requiem-r11029"
TUNE_FEATURES= "arm armv7a vfp thumb neon callconvention-hard
cortexa9"
TARGET_FPU   = "hard"
meta-bia-distro
meta-martin
meta-martin-bsp  = ":"
meta-python
meta-oe
meta-webserver
meta-filesystems = "rocko:a65c1acb1822966c3553de9fc98d8bb6be705c4e"
meta-ti  = "rocko:4a746c78c3b7060a51cd6a876f69eead363c757c"
meta-networking  = "rocko:a65c1acb1822966c3553de9fc98d8bb6be705c4e"
meta
meta-poky= "rocko:1648bcafa3d0e46acee61a34d0a07fabb85b1f8d"
meta-security-isafw  = "HEAD:489abdc65cefb566d696c8b218aa0b9b99a350ae"

NOTE: Fetching uninative binary shim from
http://downloads.yoctoproject.org/releases/uninative/1.8/x86_64-nativesdk-libc.tar.bz2;sha256sum=de4947e98e09e1432d069311cc2093974ecb9138a714fd5466f73524de66a693
Initialising tasks: 100%
||
Time: 0:00:01
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: nativesdk-u-boot-tools-v2016.03+gitAUTOINC+df61a74e68-r0 do_package:
nativesdk-u-boot-tools: chrpath command failed with exit code 7:
b'/home/martin/bia-precision-rocko/build/tmp/work/x86_64-nativesdk-biasdk-linux/nativesdk-u-boot-tools/v2016.03+gitAUTOINC+df61a74e68-r0/package/opt/bia/20180207-requiem-r11029/sysroots/x86_64-biasdk-linux/usr/bin/uboot-dumpimage:
RPATH=/home/martin/bia-precision-rocko/build/tmp/work/x86_64-nativesdk-biasdk-linux/nativesdk-u-boot-tools/v2016.03+gitAUTOINC+df61a74e68-r0/recipe-sysroot-native/usr/lib:/home/martin/bia-precision-rocko/build/tmp/work/x86_64-nativesdk-biasdk-linux/nativesdk-u-boot-tools/v2016.03+gitAUTOINC+df61a74e68-r0/recipe-sysroot-native/lib\n'b"new
rpath
'$ORIGIN/../../../../../../../home/martin/bia-precision-rocko/build/tmp/work/x86_64-nativesdk-biasdk-linux/nativesdk-u-boot-tools/v2016.03+gitAUTOINC+df61a74e68-r0/recipe-sysroot-native/usr/lib:$ORIGIN/../../../../../../../home/martin/bia-precision-rocko/build/tmp/work/x86_64-nativesdk-biasdk-linux/nativesdk-u-boot-tools/v2016.03+gitAUTOINC+df61a74e68-r0/recipe-sysroot-native/lib'
too large; maximum length 333\n"
ERROR: nativesdk-u-boot-tools-v2016.03+gitAUTOINC+df61a74e68-r0 do_package:
Function failed: perform_packagecopy
ERROR: Logfile of failure stored in:
/home/martin/bia-precision-rocko/build/tmp/work/x86_64-nativesdk-biasdk-linux/nativesdk-u-boot-tools/v2016.03+gitAUTOINC+df61a74e68-r0/temp/log.do_package.9810
ERROR: Task
(virtual:nativesdk:/home/martin/bia-precision-rocko/build/../yocto/martin/meta-martin-bsp/recipes-bsp/u-boot/u-boot-tools_2016.03.bb:do_package)
failed with exit code '1'SUMMARY = "U-Boot native tools"

Here's the recipe

LICENSE = "GPLv2+"
LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
SECTION = "bootloader"

DEPENDS = "openssl"

# This revision corresponds to the tag "v2016.03"
# We use the revision in order to avoid having to fetch it from the
# repo during parse
SRCREV = "df61a74e6845ec9bdcdd48d2aff5e9c2c6debeaa"

PV = "v2016.03+git${SRCPV}"

SRC_URI = "git://git.denx.de/u-boot.git;branch=master"

S = "${WORKDIR}/git"

EXTRA_OEMAKE_class-target = 'CROSS_COMPILE="${TARGET_PREFIX}" CC="${CC}
${CFLAGS} ${LDFLAGS}" HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}"
STRIP=true V=1'
EXTRA_OEMAKE_class-native = 'CC="${BUILD_CC} ${BUILD_CFLAGS}
${BUILD_LDFLAGS}" HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}"
STRIP=true V=1'
EXTRA_OEMAKE_class-nativesdk = 'CROSS_COMPILE="${HOST_PREFIX}" CC="${CC}
${CFLAGS} ${LDFLAGS}" HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}"
STRIP=true V=1'

do_compile () {
oe_runmake sandbox_defconfig
oe_runmake cross_tools NO_SDL=1
}

do_install () {
install -d ${D}${bindir}
# MJT: Looks like these are now part of U-Boot native package so commenting
out
#  Can remove once this is confirmed.
# install -m 0755 tools/mkimage ${D}${bindir}/uboot-mkimage
# ln -sf uboot-mkimage ${D}${bindir}/mkimage

install -m 0755 tools/mkenvimage ${D}${bindir}/uboot-mkenvimage
ln -sf uboot-mkenvimage ${D}${bindir}/mkenvimage

install -m 0755 tools/dumpimage ${D}${bindir}/uboot-dumpimage
ln -sf uboot-dumpimage ${D}${bindir}/dumpimage

install -m 0755 tools/img2brec.sh ${D}${bindir}/uboot-img2brec.sh
ln -sf uboot-img2brec.sh ${D}${bindir}/img2brec.sh

install -m 0755 tools/img2srec ${D}${bindir}/uboot-img2srec
ln -sf uboot-img2srec ${D}${bindir}/img2srec

install -m 0755 tools/jtagconsole ${D}${bindir}/uboot-jtagconsole

Re: [yocto] How to build two different kernel

[Vincent Prince]

Hi ,

You can look at the following patch
https://patchwork.openembedded.org/patch/142675

Best regards,
Vincent

2018-03-22 5:47 GMT+01:00 HuaFu 8386 :

> Hi,
>
> I want to build two different images with two different kernel configs,
> one for debug version and one for production version, like
> bitbake debug_image
> bitbake product_image
>
> Any idea how can I do that?
>
> Thanks,
> Danny
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Issues related generation of an image build with signed rpm packages

[Iván Castell]

Hello forum.

In order to generate a distro image with support for signed rpm packages, I
generated a pair of GPG keys, and setup my custom distro.conf file so Yocto
can sign packages it generates. My distro.conf file includes this:

INHERIT += "sign_rpm"
RPM_GPG_NAME = "gpgyocto"
RPM_GPG_PASSPHRASE = "passphrase"

The repo configuration file "yocto-rpm.repo" is deployed using a
dnf_%.bbappend file that copies config file into /etc/yum.repos.d:

$ cat recipes-devtools/dnf/files/yocto-rpm.repo
[yocto-rpm]
name=Rocko Yocto Repo
baseurl=http:///rpm
enabled=1
gpgcheck=1

Whenever I try to build the image, the building process generates this
error when the http web server (serving signed packages) is not running (it
is disabled):

ERROR: myimage-1.0-r0 do_rootfs: [log_check] myimage: found 1 error
message in the logfile:
[log_check] Failed to synchronize cache for repo 'yocto-rpm', disabling.


However, the image is built fine in two different scenarios:

1) when setting enabled=0 on "yocto-rpm.repo" file
2) when setting enabled=1 and running/starting the http web server.


Two questions related:

1) What? Is yocto taking into account files from the generated image
(yocto-rpm.repo) to decide how the generated image is built?
2) Why yocto needs connecting to http web server to build the image? It
shouldn't be a completely decoupled process?


Can some of you explain a bit more about this process?

Thank you in advance! :)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [matchbox-wm][PATCH] configure.ac: add lib math for composite enabled builds

[Awais Belal]

The composite enabled builds require lib math to be
present on the linker command line otherwise we get
ld: composite-engine.o: undefined reference to symbol 'exp@@GLIBC_2.2.5'
during compilation.

Signed-off-by: Awais Belal 
---
 configure.ac | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/configure.ac b/configure.ac
index dce82cc..1bc113f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -246,9 +246,11 @@ fi
 dnl -- Composite ---
 
 if test x$enable_composite != xno; then
-  PKG_CHECK_MODULES(COMPO, xcomposite xfixes xdamage xrender, ,
+  PKG_CHECK_MODULES(COMPO, xcomposite xfixes xdamage xrender, 
have_compo_deps=yes,
   AC_MSG_ERROR([*** Required Composite Librays not 
installed ***]))
-
+  if test x$have_compo_deps = xyes; then
+COMPO_LIBS="$COMPO_LIBS -lm"
+  fi
   AC_DEFINE(USE_COMPOSITE, [1], [use bleeding enge composite code])
 
 fi
-- 
2.7.4

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

Re: [yocto] [matchbox-terminal] main.c: Add support to run user command inside the terminal

[Devarsh Thakkar]

Hi Ross,

I would be glad if you could please share latest updates on this patch?
If I am correct, last status was that a build test was triggered with this 
patch.

Thanks & Regards,
Devarsh

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Wednesday, March 14, 2018 12:33 PM
To: Alexander Kanavin 
Cc: Devarsh Thakkar ; Yocto-mailing-list 
; Manjukumar Harthikote Matha ; 
vcu-team ; Devarsh Thakkar 
Subject: Re: [yocto] [matchbox-terminal] main.c: Add support to run user 
command inside the terminal

On 14 March 2018 at 18:44, Alexander Kanavin 
mailto:alexander.kana...@linux.intel.com>> 
wrote:
On 03/14/2018 04:47 PM, Devarsh Thakkar wrote:
Add support for commandline options (--command or -e)
using which one can provide commands to run inside the terminal
as shown in below command :

  $matchbox-terminal -e 
  $matchbox-terminal --command 

Ross, who (if anyone) has write access to the mathcbox repo? I think matchbox 
stuff is in a bit of limbo currently?

I do, this was having a build test earlier so I'll be pushing shortly.

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

Re: [yocto] how to add libsrtp and libsrtp-staticdev to sdk

[Burton, Ross]

That suggests that libsrtp-staticdev wasn't built.  Use
oe-pkgdata-util to determine if it was built at all: note that for
example Poky doesn't build static libraries.

(one of many reasons that people shouldn't use poky as anything but an example)

Ross

On 25 March 2018 at 14:01, Mostafa Farzane  wrote:
> Hi,
> I need to add libsrtp to my sdk. I want both static and dynamic library in
> sdk. I added "libsrtp libsrtp-staticdev" to "IMAGE_INSTALL" but getting the
> following error:
>
> Collected errors:
>  * calculate_dependencies_for: Cannot satisfy the following dependencies
> for libsrtp-staticdev:
>  *  libsrtp (= 1.5.2-r0) *
>  * opkg_solver_install: Cannot install package libsrtp-staticdev.
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [matchbox-terminal] main.c: Add support to run user command inside the terminal

[Burton, Ross]

Sorry, I failed to push.  It's now been pushed to the
matchbox-terminal repository.

Ross

On 24 March 2018 at 15:50, Devarsh Thakkar  wrote:
> Hi Ross,
>
>
>
> I would be glad if you could please share latest updates on this patch?
>
> If I am correct, last status was that a build test was triggered with this
> patch.
>
>
>
> Thanks & Regards,
>
> Devarsh
>
>
>
> From: Burton, Ross [mailto:ross.bur...@intel.com]
> Sent: Wednesday, March 14, 2018 12:33 PM
> To: Alexander Kanavin 
> Cc: Devarsh Thakkar ; Yocto-mailing-list
> ; Manjukumar Harthikote Matha ;
> vcu-team ; Devarsh Thakkar 
> Subject: Re: [yocto] [matchbox-terminal] main.c: Add support to run user
> command inside the terminal
>
>
>
> On 14 March 2018 at 18:44, Alexander Kanavin
>  wrote:
>
> On 03/14/2018 04:47 PM, Devarsh Thakkar wrote:
>
> Add support for commandline options (--command or -e)
> using which one can provide commands to run inside the terminal
> as shown in below command :
>
>   $matchbox-terminal -e 
>   $matchbox-terminal --command 
>
>
> Ross, who (if anyone) has write access to the mathcbox repo? I think
> matchbox stuff is in a bit of limbo currently?
>
>
>
> I do, this was having a build test earlier so I'll be pushing shortly.
>
>
>
> Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to check list of installed packages to stop the build process conditionally

[Iván Castell]

Yes! That's exactly what I was looking for. Thank you very much, Mr.
Vincent! :-)

2018-03-26 10:08 GMT+02:00 Vincent Prince :

> Hi,
>
> Maybe you can say A conflicts B and B conflicts A with following variable :
> https://www.yoctoproject.org/docs/current/mega-manual/mega-
> manual.html#var-RCONFLICTS
>
> Best regards,
> Vincent
>
> 2018-03-26 9:54 GMT+02:00 Iván Castell :
>
>> Hello forum.
>>
>> My layer provides two custom recipes A and B with exactly the same
>> functionality. To get a working image, one of these two recipes must be
>> included on the generated image (A_installed XOR B_installed).
>>
>> So I need the build process being able to check the list of installed
>> packages, stopping the build process in case any of these two packages is
>> included.
>>
>> Does yocto provides some mechanism to manage this issue?
>>
>> Thank you in advance!
>>
>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>


-- 




*NOTA LEGAL*
Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
contiene información de carácter confidencial exclusivamente dirigida a su
destinatario y se encuentra protegido por Ley. Cualquier persona distinta
de su destinataria tiene prohibida su reproducción, uso, divulgación, copia
o impresión total o parcial. Si ha recibido este correo electrónico por
error, se ruega lo notifique de inmediato al remitente borrando el mensaje
original juntamente con sus ficheros anexos. Gracias.

De conformidad con lo establecido en la LOPD, NAYAR SYSTEMS SL garantiza la
adopción de las medidas necesarias para asegurar el tratamiento
confidencial de los datos de carácter personal. Así mismo le informamos de
la inclusión de sus datos en un fichero bajo la responsabilidad de NAYAR
SYSTEMS SL, con la finalidad de poder atender los compromisos derivados de
la relación que mantenemos con usted. Si lo desea, puede ejercer sus
derechos de acceso, rectificación, cancelación y oposición mediante un
escrito a la siguiente dirección: i...@nayarsystems.com

*LEGAL NOTE*
This email and any attachments to it contains is confidential information
exclusively intended for the recipients. Any divulgation, copy or
distribution to third parties is prohibited without written permission of
NAYAR SYSTEMS SL. If you have received this e-mail in error, please notify
the sender immediately. In accordance with Law 15/1999 of 13 December on
the Protection of Personal Data, the NAYAR SYSTEMS SL guarantees that it
has adopted the necessary measures to ensure the confidential treatment of
personal information. We also inform you that you can exercise your access,
rectification, cancellation and opposition rights by send us a mail to:
i...@nayarsystems.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] scipy recipe

[Matthias Schöpfer]

Hi Philip,

I needed to patch numpy because scipy uses numpy.distutils a lot.

Regards,

Matthias

On 03/24/2018 05:48 PM, Philip Balister wrote:
> On 03/23/2018 06:07 AM, Matthias Schöpfer wrote:
>> Hi Peter,
>>
>> I managed to get scipy to cross compile, since I was in a hurry, and
>> have no deeper understanding of python / distutils / setuptools, it
>> turned out to be an ugly hack (but obviously I was not the first one to
>> do ugly things there ;) )
>>
>> Maybe you have had some progress as well, and we can figure out a nicer
>> solution.
>>
>> See the attached files, involving openblas, a bbappend for python-numpy
>> and python-scipy.
> 
> I'm confused why you need the bbappend for numpy?
> 
> The recipe in OE-Core should be solid without patches.
> 
> Other than that, this is very interesting stuff.
> 
> Philip
> 
> 
>>
>> Regards,
>>
>>  Matthias
>>
>>
>>
> 
> 
> 


-- 
Dr.-Ing. Matthias Schöpfer

Softwareentwicklung



IdentPro GmbH
Camp-Spich-Str. 4
53842 Troisdorf

Tel:   +49 (0)2241 / 866 392 46
Fax:   +49 (0)2241 / 866 392 99
eMail: matthias.schoep...@identpro.de

http://www.identpro.de

identplus® – Das 3D Staplerleitsystem mit enormen Sparpotenzial: z. B.
über 67.000 EUR pro Jahr bei 500 Transporten täglich! Berechnen Sie das
Einsparpotenzial für Ihr Lager mit dem identplus® Potenzialrechner.

identplus® live erleben: Vereinbaren Sie jetzt einen Termin!

-
IdentPro GmbH
Member of Dr. Wack Holding GmbH & Co.KG
Sitz und Registergericht: St. Augustin, HRB 9770 Siegburg
Geschäftsführer: Michael Wack
Umsatzsteuer-ID-Nr.: DE 254 824 945
WEEE-Reg.-Nr. DE 79026890
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to check list of installed packages to stop the build process conditionally

[Vincent Prince]

Hi,

Maybe you can say A conflicts B and B conflicts A with following variable :
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-RCONFLICTS

Best regards,
Vincent

2018-03-26 9:54 GMT+02:00 Iván Castell :

> Hello forum.
>
> My layer provides two custom recipes A and B with exactly the same
> functionality. To get a working image, one of these two recipes must be
> included on the generated image (A_installed XOR B_installed).
>
> So I need the build process being able to check the list of installed
> packages, stopping the build process in case any of these two packages is
> included.
>
> Does yocto provides some mechanism to manage this issue?
>
> Thank you in advance!
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to check list of installed packages to stop the build process conditionally

[Iván Castell]

Hello forum.

My layer provides two custom recipes A and B with exactly the same
functionality. To get a working image, one of these two recipes must be
included on the generated image (A_installed XOR B_installed).

So I need the build process being able to check the list of installed
packages, stopping the build process in case any of these two packages is
included.

Does yocto provides some mechanism to manage this issue?

Thank you in advance!
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto