[yocto] [meta-anaconda][PATCH] packagegroup-installer-x11-anaconda: use libsdl2 instead of libsdl

2019-08-19 Thread Yi Zhao
The libsdl had been moved out of oe-core because it is obsolete. Switch
to libsdl2.

Signed-off-by: Yi Zhao 
---
 recipes-installer/packagegroups/packagegroup-installer-x11-anaconda.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/recipes-installer/packagegroups/packagegroup-installer-x11-anaconda.bb 
b/recipes-installer/packagegroups/packagegroup-installer-x11-anaconda.bb
index 87c57c9..aa53809 100644
--- a/recipes-installer/packagegroups/packagegroup-installer-x11-anaconda.bb
+++ b/recipes-installer/packagegroups/packagegroup-installer-x11-anaconda.bb
@@ -18,7 +18,7 @@ RDEPENDS_packagegroup-installer-x11-anaconda = "\
 xset \
 settings-daemon \
 xrandr \
-libsdl \
+libsdl2 \
 metacity \
 adwaita-icon-theme \
 pango \
-- 
2.7.4

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


Re: [yocto] quilt-native-0.64-r0 do_install: oe_runmake failed

2019-08-19 Thread Khem Raj
error return code 126 means  Command invoked cannot execute so my
guess is the script is not marked executable. so may be try something
like

do_install_prepend() {
  chmod +x config/install-sh
}

On Mon, Aug 19, 2019 at 2:37 AM Pushpendra singh
 wrote:
>
> Hi,
>
> I am using Ubantu - 16.04 as an host machine
>
> Xilinx SDK Version : 2017.3
>
> Command : bitbake petalinux-image-minimal
>
> Getting below error
>
> Parsing recipes: 100% 
> |###|
>  Time: 0:09:00
> Parsing of 2463 .bb files complete (0 cached, 2463 parsed). 3256 targets, 229 
> skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION = "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "aarch64-poky-linux"
> MACHINE = "zcu102-zynqmp"
> DISTRO = "poky"
> DISTRO_VERSION = "2.2.2"
> TUNE_FEATURES = "aarch64"
> TARGET_FPU = ""
> meta
> meta-poky = "rel-v2017.3:8506cec55de8950e89a4d3e786860f1086782587"
> meta-perl
> meta-systemd
> meta-gpe
> meta-python
> meta-efl
> meta-ruby
> meta-filesystems
> meta-gnome
> meta-multimedia
> meta-networking
> meta-webserver
> meta-xfce
> meta-initramfs
> meta-oe = "rel-v2017.3:a9887ac249b81fcac3007244d0c807c71b73acef"
> meta-linaro-toolchain = "rel-v2017.3:39860f6c7af0858981cc004bbe4f4c421f6be607"
> meta-qt5 = "rel-v2017.3:eec778bfb9a0b5494d593a2d7bb02c027b641835"
> meta-xilinx = "rel-v2017.3:04a45809e0bc42b35c88f8a08305d82fd25e97cf"
> meta-xilinx-tools = "rel-v2017.3:37eff634934efac72d3e2eabb7c4f8d0c8a36fbb"
> meta-petalinux = "rel-v2017.3:d74ceaef26e606c2761edfc3446d0ad3c3cc8b8e"
> meta-virtualization = "rel-v2017.3:cbfd4376d5e9d229f857151ffdfb57fbc6c0c40d"
> meta-openamp = "rel-v2017.3:cfeca8988418e4967f0d6df828d23a1540ae25a0"
>
> Initialising tasks: 100% 
> ||
>  Time: 0:00:21
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: quilt-native-0.64-r0 do_install: oe_runmake failed
> ERROR: quilt-native-0.64-r0 do_install: Function failed: do_install (log file 
> is located at 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_install.15836)
> ERROR: Logfile of failure stored in: 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_install.15836
> Log data follows:
> | DEBUG: Executing shell function do_install
> | NOTE: make -j 2 
> BUILD_ROOT=/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image
>  install
> | ERROR: oe_runmake failed
> | config/install-sh -c -d 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/sysroots/x86_64-linux/usr/bin
> | rm -rf 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/sysroots/x86_64-linux/usr/share/quilt/compat
> | /bin/bash: config/install-sh: Permission denied
> | Makefile:305: recipe for target 'install-main' failed
> | make: *** [install-main] Error 126
> | make: *** Waiting for unfinished jobs
> | config/install-sh -c -d 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/sysroots/x86_64-linux/usr/share/quilt/compat
> | /bin/bash: config/install-sh: Permission denied
> | Makefile:346: recipe for target 'install-compat1' failed
> | make: *** [install-compat1] Error 126
> | WARNING: 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/run.do_install.15836:1
>  exit 1 from 'exit 1'
> | ERROR: Function failed: do_install (log file is located at 
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_install.15836)
> ERROR: Task 
> (/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/sources/core/meta/recipes-devtools/quilt/quilt-native_0.64.bb:do_install)
>  failed with exit code '1'
> NOTE: Tasks Summary: Attempted 15 tasks of which 13 didn't need to be rerun 
> and 1 failed.
>
> Summary: 1 task failed:
> /home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/sources/core/meta/recipes-devtools/quilt/quilt-native_0.64.bb:do_install
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctop

Re: [yocto] Your GStreamer installation is missing a plug-in

2019-08-19 Thread Khem Raj
might be you need to install gstreamer1.0-omx on target.

On Mon, Aug 19, 2019 at 12:48 AM Bhupendra Singh
 wrote:
>
> Dear All
>
> I am trying to make a Qt application QML-GUI that will show live streaming of 
> ip-camera. but when in run qt-application on my Embedded Device then I got
>
> Some problem .
>
>
>
> (gst-plugin-scanner:1296): GStreamer-WARNING **: Failed to load plugin 
> '/usr/lib/gstreamer-0.10/libgstopengl.so': /usr/lib/libgstgl-0.10.so.1: 
> undefined symbol: gst_gl_shader_set_uniform_matrix_2x3fv
>
> ** (gst-plugin-scanner:1296): WARNING **: could not find config file 
> '/home/root/.config/gst-openmax.conf'.. using defaults!
>
> (gst-plugin-scanner:1296): GLib-GObject-WARNING **: cannot register existing 
> type 'GstVorbisDec'
>
> (gst-plugin-scanner:1296): GLib-CRITICAL **: g_once_init_leave: assertion 
> 'result != 0' failed
>
> (gst-plugin-scanner:1296): GStreamer-CRITICAL **: gst_element_register: 
> assertion 'g_type_is_a (type, GST_TYPE_ELEMENT)' failed
>
> shared memfd open() failed: Function not implemented
>
> Warning: "No decoder available for type 'application/x-rtp, 
> media=(string)video, payload=(int)35, clock-rate=(int)9, 
> encoding-name=(string)H264, packetization-mode=(string)1, 
> profile-level-id=(string)4d0029, 
> sprop-parameter-sets=(string)\"Z00AKZpkA8ARPy4C1AQEFAg\\=\\,aO48gA\\=\\=\", 
> a-recvonly=(string)\"\", npt-start=(guint64)0, play-speed=(double)1, 
> play-scale=(double)1'."
>
> Error: "Your GStreamer installation is missing a plug-in."
>
>
>
> I am using –
>
> Embedded Device(SOC) – Colibri-T20  (NVIDIA,Toradex)
>
> Os -Angstrom v2017.12 – Kernel
>
> Colibri-T20_Qt5-X11-Image 2.8b6 20190816
>
>
>
> Which package I am missing in my os
>
> If am running this application on my Desktop it works correctly .
>
>
>
>
>
> Thanks & Regards
>
> Bhupendra Singh
>
>
>
> --
> ___
> 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] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2019-08-19 Thread sjolley.yp.pm
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 297
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

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


Re: [yocto] Segmentation fault | bitbake machine-image.bb | core dumped

2019-08-19 Thread Randy MacLeod

On 8/19/19 12:33 AM, jaymin.da...@vivaldi.net wrote:

Hi Randy,

Thanks for info.
But, as you can see from previous logs, I was getting core dumped issue 
at the time of bitbake (while building the image).

How can I find the cause of this type of core dumped?


Hi Jaymin,

While I'd like to help you with each step, I'm usually not going
to do that (unless you become a Wind River customer. :) )


To save us and anyone who might be reading this thread some time,
it looks like the program you are having trouble with is from a
meta-android layer or elsewhere. On ubuntu it's packaged in
android-sdk-ext4-utils:
   $ make_ext4fs

   Command 'make_ext4fs' not found, but can be installed with:

   sudo apt install android-sdk-ext4-utils  # version 8.1.0+r23-2, or
   sudo apt install android-tools-fsutils   # version 5.1.1.r38-1.1

Please read the rest of this email and let us know if you added
that layer into your conf/bblayers.conf file for reference.


Good luck,
../Randy


So, I wanted to confirm that bitbake wasn't preventing the
core file from being generated, so I used a private machine running
ubuntu-19.04 and replaced the gcc executable with my own program
as shown below. Since you already have an error happening,
you don't have to do this.


Here's my simple program in /tmp/hw.c

#include 
#include 

void  do_segv() {
  int *psplat = 0;
  int x = -1;
  x = *psplat;
}


int main(int c, char *v[]) {
  printf("Hello world\n");
  do_segv();

  exit(0);
}

Compile it:
gcc -g -o /tmp/hw /tmp/hw.c

Now set the kernel's core_pattern as explained in:
http://www.linuxhowtos.org/Tips%20and%20Tricks/coredump.htm

$ sudo su -
First save the old pattern:
# cat /proc/sys/kernel/core_pattern  > /root/old-core-pattern
# echo "core.%e.%p" > /proc/sys/kernel/core_pattern
# exit

Under your own user id:
$ ulimit -c unlimited

$ Test that we can generate a core dump outside of bitbake:
$ /tmp/hw
Hello world
Segmentation fault (core dumped)
$ file core.hw.20982
core.hw.20982: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), 
SVR4-style, from '/tmp/hw', real uid: ..., execfn: '/tmp/hw', platform: 
'x86_64'


$ gdb /tmp/hw core.hw*
...

...
Reading symbols from /tmp/hw...
[New LWP 20982]
Core was generated by `/tmp/hw'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x55af3c18617a in do_segv () at /tmp/hw.c:12
12x = *psplat;
(gdb) bt
#0  0x55af3c18617a in do_segv () at /tmp/hw.c:12
#1  0x55af3c1861a7 in main (c=1, v=0x7ffc801bfc38) at /tmp/hw.c:20
(gdb)



So, now I want to use this as a test to confirm that I can generate
a core file when running bitbake to simulate your problem. In your
case, everything is setup so that you should be able to start debugging 
'make_ext4fs' but running bitbake, getting a core file, then running:

$ gdb make_ext4fs /path/to/core.pattern


I know that the OS doesn't depend on having a functioning compiler all
the time so I'm going to *save*, then over-write the compiler. You call
'gcc' to compile a program but it's actually a series of links on my
Ubuntu distro:

$ ls -l /usr/bin/gcc
lrwxrwxrwx 1 root root 5 Apr  4 00:23 /usr/bin/gcc -> gcc-8
$ ls -l /usr/bin/gcc-8
lrwxrwxrwx 1 root root 22 Apr  6 11:04 /usr/bin/gcc-8 -> 
x86_64-linux-gnu-gcc-8

$ ls -l /usr/bin/x86_64-linux-gnu-gcc-8
-rwxr-xr-x 1 root root 19336 Aug 19 14:53 /usr/bin/x86_64-linux-gnu-gcc-8


Copy the simple test program over the compiler executable BUT ...

SAVE IT FIRST!!!


# WARNING: only do this on a system that other people are not using:
$ sudo mv /usr/bin/x86_64-linux-gnu-gcc-8 \
  /usr/bin/x86_64-linux-gnu-gcc-8.orig
$ sudo cp /tmp/hw /usr/bin/x86_64-linux-gnu-gcc-8

Now, I know that m4-native is one of the first programs that use gcc
so I can run:
$ bitbake -c configure m4-native

...


| checking whether the C compiler works... no
| configure: error: in 
`/home/rmacleod/tmp/yp/b/test-ulimit/tmp-glibc/work/x86_64-linux/m4-native/1.4.18-r0/build':

| configure: error: C compiler cannot create executables
| See `config.log' for more details
| WARNING: exit code 1 from a shell command.
|
ERROR: Task 
(/home/rmacleod/tmp/yp/oe-core.git/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_configure) 
failed with exit code '1'
NOTE: Tasks Summary: Attempted 29 tasks of which 28 didn't need to be 
rerun and 1 failed.


Summary: 1 task failed:

/home/rmacleod/tmp/yp/oe-core.git/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_configure
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

$ find * -name "core*"
tmp-glibc/work/x86_64-linux/m4-native/1.4.18-r0/build/core.gcc.21823
...
tmp-glibc/work/x86_64-linux/m4-native/1.4.18-r0/build/core.gcc.21808


So core files are being generated.

Now to restore the distro:
$ sudo su -
# rm /usr/bin/x86_64-linux-gnu-gcc-8
# mv /usr/bin/x86_64-linux-gnu-gcc-8.orig /usr/bin/x86_64-linux-gnu-gcc-8

# cat /root/old-core-pattern
|/usr/share/apport/apport %p %s %c %d %P
# echo "| /usr/share/apport/apport %p %s %c %d %P" > 
/proc/

Re: [yocto] [OE-core] Yocto Project Summit at ELCE Call for Particpation

2019-08-19 Thread Paul Barker
Hey folks,

I'm looking to submit a talk and I'm a little confused on when to register for 
the YP summit. Should I register now to get the discounted rate or should I 
wait until the list of accepted speakers is announced? Unlike for the main 
conference, it looks like the registration price goes up before the list of 
accepted speakers is released. It's also not very clear whether accepted 
speakers will be given complimentary registration.

Thanks,
Paul

On Mon, 19 Aug 2019, at 12:21, Nicolas Dechesne wrote:
> hi Philip,
> 
> thanks for sending this out!
> 
> On Mon, Aug 19, 2019 at 3:17 AM Philip Balister  wrote:
> >
> > At the past few OopenEmbedded developer meetings, people have been
> > asking for more developer and user focused events like a miniconf.
> > Partly based on this feedback, there is a two day event sponsored by the
> > Yocto Project that provides a chance for people to talk about the Yocto
> > Project and OpenEmbedded. The CFP is a bit buried on the page and I like
> > to get it more exposure, so here the direct link:
> 
> all information about the Summit is also available here now:
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_Summit_2019
> 
> >
> > https://events.linuxfoundation.org/wp-content/uploads/2019/08/Yocto-Project-Summit-2019-CFP-1.pdf
> >
> > We'd like to see new faces talking. We know there are a lot of good
> > stories out there, that will help lots of people become better users and
> > developers.
> >
> > The link to the event is here:
> >
> > https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/
> >
> > Follow the path to the Yocto Project Summit. If you are alrady signed up
> > for ELCE, you should be able to update your registration to include the
> > Summit.
> >
> > Philip
> > --
> > ___
> > Openembedded-core mailing list
> > openembedded-c...@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> -- 
> ___
> Openembedded-core mailing list
> openembedded-c...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

-- 
Paul Barker
Managing Director & Principal Engineer
Beta Five Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH] In Yocto 2.7 powertop package is broken.

2019-08-19 Thread Martin Jansa
See
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg126436.html

On Mon, Aug 19, 2019 at 11:35 AM Kaz Kylheku  wrote:

> Hi all,
>
> Via a .bbappend file in my own layers, I added the following patch to
> build powertop, which is enabled when tools-profile is added to
> EXTRA_IMAGE_FEATURES.
>
> * recipes-profiling/powertop/files/posix-path-max-not-defined.patch:
> Patch for build issue. The C++ code needs to including  which
> defines the POSIX PATH_MAX preprocessor symbol.
>
> Index: powertop-v2.10/src/wakeup/wakeup_ethernet.h
> ===
> --- powertop-v2.10.orig/src/wakeup/wakeup_ethernet.h
> +++ powertop-v2.10/src/wakeup/wakeup_ethernet.h
> @@ -25,6 +25,7 @@
>   #ifndef _INCLUDE_GUARD_ETHERNET_WAKEUP_H
>   #define _INCLUDE_GUARD_ETHERNET_WAKEUP_H
>
> +#include 
>   #include 
>
>   #include "wakeup.h"
> Index: powertop-v2.10/src/wakeup/wakeup_usb.h
> ===
> --- powertop-v2.10.orig/src/wakeup/wakeup_usb.h
> +++ powertop-v2.10/src/wakeup/wakeup_usb.h
> @@ -26,6 +26,7 @@
>   #define _INCLUDE_GUARD_USB_WAKEUP_H
>
>   #include 
> +#include 
>
>   #include "wakeup.h"
>
>
> --
> ___
> 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] [meta-raspberrypi] Issues building bcm2835_bootfiles in Thud

2019-08-19 Thread Andrei Gherzan
Hello,

On 14/08/2019 17.39, Phillip Marks wrote:
> We are building Thud for a raspberry-pi0+wifi and we've noticed that
> the recipe bcm2835_bootfiles
> under meta-raspberrypi/recipes-bsp/bootfiles is not pulling in the
> proprietary *.dtb modules from the firmware repository. This is
> causing linux-raspberrypi to fail as it tries to build those modules
> and fails on "no target found for bcm2708-rpi-0-w.dtb". How does
> bcm2835_bootfiles pull in the Broadcom firmware modules and where in
> build does it store them? We don't see them in tmp/work. 
>
Are you using a clean thud setup or updating the kernel to the current
HEAD? You shouldn't hit this issue following the versions use in the
thud branch of meta-raspberrypi. Long story short, the build system
doesn't take advantage of the precompiled dtb files available in the
Raspberry Pi firmware repository. It maintains a list of dtb as a
variable and compiles them while compiling the kernel. I suspect that
you have a bbappend which updates the kernel to current HEAD (includes a
dtb rename backport).

-- 
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan

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


Re: [yocto] Opencv headers

2019-08-19 Thread Ekaterini Voulgari

Indeed.Grazie.

On 19/8/19 2:20 μ.μ., Gabriele Zampieri wrote:

Hi,

you need to add
DEPENDS = "opencv"
to your recipe. This will import the needed header in your recipe sysroot.

Best regards,
Gabriele

Il giorno lun 19 ago 2019 alle ore 13:09 Ekaterini Voulgari 
mailto:sdi1100...@di.uoa.gr>> ha scritto:


Hello all,
I'm trying to add a program to my image that uses opencv (#include
), but I get compile error "fatal error:
opencv2/opencv.hpp: No such file or directory"

The file opencv.hpp exists in workdir

/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-musleabi/opencv/3.4.5-r0/image/usr/include/opencv2/opencv.hpp.

Can anyone help on where are the headers located in crossbuilds? Any
help appreciated.
The recipe:

SRC_URI = "file://capture.cpp"

do_compile () {
 ${CC} capture.cpp  -lopencv_core -lopencv_imgproc
-lopencv_highgui
-lopencv_videoio
}

do_install () {

 install -d -m 0755 ${D}/${bindir}
 install -m 0755 prog_kameras ${D}/${bindir}/prog_kameras
}

-- 
___

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] [meta-mingw] QEMU on thud mingw SDK is broken

2019-08-19 Thread Sinan Kaya


I noticed last week that qemu packaged into mingw sdk is broken while
the qemu in linux sdk works fine.

Qemu crashes very early while launching the kernel boot.
This used to work fine on sumo.

Does anybody see this problem too?


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


Re: [yocto] [OE-core] Yocto Project Summit at ELCE Call for Particpation

2019-08-19 Thread Nicolas Dechesne
hi Philip,

thanks for sending this out!

On Mon, Aug 19, 2019 at 3:17 AM Philip Balister  wrote:
>
> At the past few OopenEmbedded developer meetings, people have been
> asking for more developer and user focused events like a miniconf.
> Partly based on this feedback, there is a two day event sponsored by the
> Yocto Project that provides a chance for people to talk about the Yocto
> Project and OpenEmbedded. The CFP is a bit buried on the page and I like
> to get it more exposure, so here the direct link:

all information about the Summit is also available here now:

https://wiki.yoctoproject.org/wiki/Yocto_Project_Summit_2019

>
> https://events.linuxfoundation.org/wp-content/uploads/2019/08/Yocto-Project-Summit-2019-CFP-1.pdf
>
> We'd like to see new faces talking. We know there are a lot of good
> stories out there, that will help lots of people become better users and
> developers.
>
> The link to the event is here:
>
> https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/
>
> Follow the path to the Yocto Project Summit. If you are alrady signed up
> for ELCE, you should be able to update your registration to include the
> Summit.
>
> Philip
> --
> ___
> Openembedded-core mailing list
> openembedded-c...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Opencv headers

2019-08-19 Thread Gabriele Zampieri
Hi,

you need to add
DEPENDS = "opencv"
to your recipe. This will import the needed header in your recipe sysroot.

Best regards,
Gabriele

Il giorno lun 19 ago 2019 alle ore 13:09 Ekaterini Voulgari <
sdi1100...@di.uoa.gr> ha scritto:

> Hello all,
> I'm trying to add a program to my image that uses opencv (#include
> ), but I get compile error "fatal error:
> opencv2/opencv.hpp: No such file or directory"
>
> The file opencv.hpp exists in workdir
> /build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-musleabi/opencv/3.4.5-r0/image/usr/include/opencv2/opencv.hpp.
>
> Can anyone help on where are the headers located in crossbuilds? Any
> help appreciated.
> The recipe:
>
> SRC_URI = "file://capture.cpp"
>
> do_compile () {
>  ${CC} capture.cpp  -lopencv_core -lopencv_imgproc -lopencv_highgui
> -lopencv_videoio
> }
>
> do_install () {
>
>  install -d -m 0755 ${D}/${bindir}
>  install -m 0755 prog_kameras ${D}/${bindir}/prog_kameras
> }
>
> --
> ___
> 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] Opencv headers

2019-08-19 Thread Ekaterini Voulgari

Hello all,
I'm trying to add a program to my image that uses opencv (#include 
), but I get compile error "fatal error: 
opencv2/opencv.hpp: No such file or directory"


The file opencv.hpp exists in workdir 
/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-musleabi/opencv/3.4.5-r0/image/usr/include/opencv2/opencv.hpp. 
Can anyone help on where are the headers located in crossbuilds? Any 
help appreciated.

The recipe:

SRC_URI = "file://capture.cpp"

do_compile () {
    ${CC} capture.cpp  -lopencv_core -lopencv_imgproc -lopencv_highgui 
-lopencv_videoio

}

do_install () {

    install -d -m 0755 ${D}/${bindir}
    install -m 0755 prog_kameras ${D}/${bindir}/prog_kameras
}

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


[yocto] Yocto Project Summit at ELCE Call for Particpation

2019-08-19 Thread Philip Balister
At the past few OopenEmbedded developer meetings, people have been
asking for more developer and user focused events like a miniconf.
Partly based on this feedback, there is a two day event sponsored by the
Yocto Project that provides a chance for people to talk about the Yocto
Project and OpenEmbedded. The CFP is a bit buried on the page and I like
to get it more exposure, so here the direct link:

https://events.linuxfoundation.org/wp-content/uploads/2019/08/Yocto-Project-Summit-2019-CFP-1.pdf

We'd like to see new faces talking. We know there are a lot of good
stories out there, that will help lots of people become better users and
developers.

The link to the event is here:

https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/

Follow the path to the Yocto Project Summit. If you are alrady signed up
for ELCE, you should be able to update your registration to include the
Summit.

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


Re: [yocto] Ticket Purchasing Yocto Conference in Lyon

2019-08-19 Thread Alexander Kanavin
On Mon, 19 Aug 2019 at 11:38,  wrote:

> some of our colleagues would like to join the yocto after the linux
> embedded. Unfortuntely I can’t find any website or link where a ticket
> purchasing is possible. Is it possible to receive any information on the
> purchasing process and when it will start?
>

It is right here:
https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/

There is a link that lets you modify an existing registration by adding
'extras' to it, and yocto summit is one such. You need a registration code
for the original conference that came with the confirmation email.

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


[yocto] Qemu on windows sdk

2019-08-19 Thread franksinankaya
I noticed last week that qemu packaged into mingw windows sdk is broken while 
the qemu in linux sdk works fine using thud-next branch. Qemu crashes very 
early while launching the kernel boot. This used to work fine on sumo.Does 
anybody see this problem too?-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-raspberrypi] Issues building bcm2835_bootfiles in Thud

2019-08-19 Thread Phillip Marks
We are building Thud for a raspberry-pi0+wifi and we've noticed that the
recipe bcm2835_bootfiles under meta-raspberrypi/recipes-bsp/bootfiles is
not pulling in the proprietary *.dtb modules from the firmware repository.
This is causing linux-raspberrypi to fail as it tries to build those
modules and fails on "no target found for bcm2708-rpi-0-w.dtb". How does
bcm2835_bootfiles pull in the Broadcom firmware modules and where in build
does it store them? We don't see them in tmp/work.

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


[yocto] Ticket Purchasing Yocto Conference in Lyon

2019-08-19 Thread julia . ghelych-khani
Hi,

some of our colleagues would like to join the yocto after the linux embedded. 
Unfortuntely I can't find any website or link where a ticket purchasing is 
possible. Is it possible to receive any information on the purchasing process 
and when it will start?

Thank you very much in advance.

Best,
Julia

[cid:image001.png@01D4CD14.15B4AFB0]

Julia Ghelych-Khani | 
julia.ghelych-kh...@daimler.com | +49 
(176) 309 921 75 | Assistant to Head of Embedded & Frontend Technology | 
MBition GmbH | Dovestraße 1, 10587 Berlin, Germany
Geschäftsführer/Board of Directors: Gregor Zetsche, Falco Gottwald, 
Registergericht/Court of Registry: Amtsgericht Charlottenburg 
HRB-Nr./Commercial Register No.: 188241 B




If you are not the addressee, please inform us immediately that you have 
received this e-mail by mistake, and delete it. We thank you for your support.

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


[yocto] quilt-native-0.64-r0 do_install: oe_runmake failed

2019-08-19 Thread Pushpendra singh
Hi,

I am using Ubantu - 16.04 as an host machine

Xilinx SDK Version : 2017.3

Command : bitbake petalinux-image-minimal

Getting below error

Parsing recipes: 100%
|###|
Time: 0:09:00
Parsing of 2463 .bb files complete (0 cached, 2463 parsed). 3256 targets,
229 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "zcu102-zynqmp"
DISTRO = "poky"
DISTRO_VERSION = "2.2.2"
TUNE_FEATURES = "aarch64"
TARGET_FPU = ""
meta
meta-poky = "rel-v2017.3:8506cec55de8950e89a4d3e786860f1086782587"
meta-perl
meta-systemd
meta-gpe
meta-python
meta-efl
meta-ruby
meta-filesystems
meta-gnome
meta-multimedia
meta-networking
meta-webserver
meta-xfce
meta-initramfs
meta-oe = "rel-v2017.3:a9887ac249b81fcac3007244d0c807c71b73acef"
meta-linaro-toolchain =
"rel-v2017.3:39860f6c7af0858981cc004bbe4f4c421f6be607"
meta-qt5 = "rel-v2017.3:eec778bfb9a0b5494d593a2d7bb02c027b641835"
meta-xilinx = "rel-v2017.3:04a45809e0bc42b35c88f8a08305d82fd25e97cf"
meta-xilinx-tools = "rel-v2017.3:37eff634934efac72d3e2eabb7c4f8d0c8a36fbb"
meta-petalinux = "rel-v2017.3:d74ceaef26e606c2761edfc3446d0ad3c3cc8b8e"
meta-virtualization = "rel-v2017.3:cbfd4376d5e9d229f857151ffdfb57fbc6c0c40d"
meta-openamp = "rel-v2017.3:cfeca8988418e4967f0d6df828d23a1540ae25a0"

Initialising tasks: 100%
||
Time: 0:00:21
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: quilt-native-0.64-r0 do_install: oe_runmake failed
ERROR: quilt-native-0.64-r0 do_install: Function failed: do_install (log
file is located at
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_install.15836)
ERROR: Logfile of failure stored in:
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_install.15836
Log data follows:
| DEBUG: Executing shell function do_install
| NOTE: make -j 2
BUILD_ROOT=/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image
install
| ERROR: oe_runmake failed
| config/install-sh -c -d
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/sysroots/x86_64-linux/usr/bin
| rm -rf
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/sysroots/x86_64-linux/usr/share/quilt/compat
| /bin/bash: config/install-sh: Permission denied
| Makefile:305: recipe for target 'install-main' failed
| make: *** [install-main] Error 126
| make: *** Waiting for unfinished jobs
| config/install-sh -c -d
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/image/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/sysroots/x86_64-linux/usr/share/quilt/compat
| /bin/bash: config/install-sh: Permission denied
| Makefile:346: recipe for target 'install-compat1' failed
| make: *** [install-compat1] Error 126
| WARNING:
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/run.do_install.15836:1
exit 1 from 'exit 1'
| ERROR: Function failed: do_install (log file is located at
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/build/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_install.15836)
ERROR: Task
(/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/sources/core/meta/recipes-devtools/quilt/quilt-native_0.64.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 15 tasks of which 13 didn't need to be rerun
and 1 failed.

Summary: 1 task failed:
/home/pre-si-user/Desktop/Pushpendra/Xilix_Zync/Yocto_Code/sources/core/meta/recipes-devtools/quilt/quilt-native_0.64.bb:
do_install
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [PATCH] In Yocto 2.7 powertop package is broken.

2019-08-19 Thread Kaz Kylheku

Hi all,

Via a .bbappend file in my own layers, I added the following patch to
build powertop, which is enabled when tools-profile is added to
EXTRA_IMAGE_FEATURES.

* recipes-profiling/powertop/files/posix-path-max-not-defined.patch:
Patch for build issue. The C++ code needs to including  which
defines the POSIX PATH_MAX preprocessor symbol.

Index: powertop-v2.10/src/wakeup/wakeup_ethernet.h
===
--- powertop-v2.10.orig/src/wakeup/wakeup_ethernet.h
+++ powertop-v2.10/src/wakeup/wakeup_ethernet.h
@@ -25,6 +25,7 @@
 #ifndef _INCLUDE_GUARD_ETHERNET_WAKEUP_H
 #define _INCLUDE_GUARD_ETHERNET_WAKEUP_H

+#include 
 #include 

 #include "wakeup.h"
Index: powertop-v2.10/src/wakeup/wakeup_usb.h
===
--- powertop-v2.10.orig/src/wakeup/wakeup_usb.h
+++ powertop-v2.10/src/wakeup/wakeup_usb.h
@@ -26,6 +26,7 @@
 #define _INCLUDE_GUARD_USB_WAKEUP_H

 #include 
+#include 

 #include "wakeup.h"


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


Re: [yocto] [yocto-autobuilder2][PATCH 2/3] Added remote distribution of config JSON files

2019-08-19 Thread Richard Purdie
On Tue, 2019-07-30 at 14:36 -0400, Thomas Goodwin wrote:
> This feature/fix allows the worker to download the
> autobuilder helper JSON files from the controller
> rather than having to store them in the
> yocto-autobuilder-helper repository.  The process
> installs the file into the worker's
> builddir/yocto-autobuilder-helper path.
> 
> Signed-off-by: Thomas Goodwin 
> ---
>  builders.py | 22 ++
>  1 file changed, 22 insertions(+)

I like the idea however this is going to break the autobuilders as they
already use full paths in the variable.

I've merged some of the other patches but this one will need a little
further thought so we don't break the existing install.

The existing code also allows for different path locations on
individual workers (e.g. different username) which this would break.

Cheers,

Richard

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


[yocto] Your GStreamer installation is missing a plug-in

2019-08-19 Thread Bhupendra Singh
Dear All

I am trying to make a Qt application QML-GUI that will show live streaming
of ip-camera. but when in run qt-application on my Embedded Device then I
got 

Some problem .   

 

(gst-plugin-scanner:1296): GStreamer-WARNING **: Failed to load plugin
'/usr/lib/gstreamer-0.10/libgstopengl.so': /usr/lib/libgstgl-0.10.so.1:
undefined symbol: gst_gl_shader_set_uniform_matrix_2x3fv

** (gst-plugin-scanner:1296): WARNING **: could not find config file
'/home/root/.config/gst-openmax.conf'.. using defaults!

(gst-plugin-scanner:1296): GLib-GObject-WARNING **: cannot register existing
type 'GstVorbisDec'

(gst-plugin-scanner:1296): GLib-CRITICAL **: g_once_init_leave: assertion
'result != 0' failed

(gst-plugin-scanner:1296): GStreamer-CRITICAL **: gst_element_register:
assertion 'g_type_is_a (type, GST_TYPE_ELEMENT)' failed

shared memfd open() failed: Function not implemented

Warning: "No decoder available for type 'application/x-rtp,
media=(string)video, payload=(int)35, clock-rate=(int)9,
encoding-name=(string)H264, packetization-mode=(string)1,
profile-level-id=(string)4d0029,
sprop-parameter-sets=(string)\"Z00AKZpkA8ARPy4C1AQEFAg\\=\\,aO48gA\\=\\=\",
a-recvonly=(string)\"\", npt-start=(guint64)0, play-speed=(double)1,
play-scale=(double)1'."

Error: "Your GStreamer installation is missing a plug-in."

 

I am using -

Embedded Device(SOC) - Colibri-T20  (NVIDIA,Toradex)

Os -Angstrom v2017.12 - Kernel   

Colibri-T20_Qt5-X11-Image 2.8b6 20190816

 

Which package I am missing in my os

If am running this application on my Desktop it works correctly .

 

 

Thanks & Regards

Bhupendra Singh

 

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


[yocto] Recipe svn-fetcher and scmdata

2019-08-19 Thread Teemu K
Hi,

I have some recipes that fetch sources directly from svn. I'd like to
keep the .svn to make it easier to commit changes. I checked that
those are by default removed and that there is scmdata - option if
those wanted to be kept.

I set the following src_uri:

SRC_URI = 
"svn://my.svn.server/svn/sw_components/program/;module=trunk;protocol=http;scmdata=keep"

Yet the .svn - data is removed from the sources under build -
directory. It is in under download directory though so I'm wondering
if I got this right in the first place?

I tried with devtool modify and it seems I ended up having .git -
directory there although sources are in svn. Maybe it's systems
'subtle' way of telling me to switch to git? ;)

But should the scmdata=keep option work like I'm thinking it should
and/or what I'm doing wrong?

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