Re: [yocto] qemu segmentation fault on gobject-introspection

2019-02-20 Thread Khem Raj
On Wed, Feb 20, 2019 at 3:51 PM João Gonçalves wrote: > Hello, > when trying to migrate my build to master branch of oe layers I got this > qemu segmentation fault during gobject-introspection. > Does anyone have any clue on this? > This error means qemu is crashing while running some user mode

[yocto] qemu segmentation fault on gobject-introspection

2019-02-20 Thread João Gonçalves
Hello, when trying to migrate my build to master branch of oe layers I got this qemu segmentation fault during gobject-introspection. Does anyone have any clue on this? Thank you, João Gonçalves | qemu: uncaught target signal 11 (Segmentation fault) - core dumped | Segmentation fault (core

Re: [yocto] [EXTERNAL] Problems using MIRRORS variables

2019-02-20 Thread Smith, Virgil (US)
Quick _workaround_: 1. Modify/extend your Repo manifest to pull your mirror repos to the appropriate place under downloads/git2. 2. Override the non-sha1 SRCREVs with an appropriate SHA1. Either in .bbappend files or via conf file extensions. The mega-manual describes the latter in

[yocto] [meta-mingw][PATCH] classes/toolchain-scripts-mingw32: Fix bad cmd flag

2019-02-20 Thread Joshua Watt
The command to properly set the exit code at the end of the toolchain environment was using the correct flag delimiter '/', but the code to coerce all the unix-style paths to windows paths was incorrectly changing this to a '\'. This worked find in wines cmd, but on an actual Windows host, this

[yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7

2019-02-20 Thread Joshua Watt
Upgrade diffutils from 3.6 to 3.7. The upstream made several fixes so the local patches are no longer necessary, but the gnulib-tests need to be dropped since they do not compile properly. Since there are no more local patches, the bbappend can be made to match all versions. Signed-off-by: Joshua

Re: [yocto] local.conf confusion

2019-02-20 Thread Greg Wilson-Lindberg
Well, I'm feeling bad, the Yocto system that I'm using is from Qt for their Boot2Qt builds. It seems that the include is pointing their private dir tree. Sorry for bothering the list with this noise. Regards, Greg Wilson-Lindberg  > -Original Message- > From: Greg Wilson-Lindberg >

Re: [yocto] local.conf confusion

2019-02-20 Thread Rudolf J Streif
Greg, I am not entirely sure why you are including a machine configuration include file into your conf/local.conf file. However, the "include" directive is optional include and hence if the file is not found Bitbake will not raise an error and terminate. If you need that behavior use "require"

[yocto] local.conf confusion

2019-02-20 Thread Greg Wilson-Lindberg
Hello list, I've run into a confusion that should be simple. I've got a build based on sumo, at the bottom of my local.conf file is the line: include conf/distro/include/${MACHINE}.pre.inc This should be straight forward, just find the conf/distro/include directory and all of the *.pre.inc

Re: [yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7

2019-02-20 Thread Joshua Watt
On Wed, 2019-02-20 at 19:13 +0100, Alexander Kanavin wrote: > On Wed, 20 Feb 2019 at 19:08, Joshua Watt > wrote: > > .../diffutils/diffutils/sdiff-no-kill.patch | 32 - > > -- > > .../diffutils/diffutils_3.6.bbappend | 18 --- > >

Re: [yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7

2019-02-20 Thread Alexander Kanavin
On Wed, 20 Feb 2019 at 19:08, Joshua Watt wrote: > .../diffutils/diffutils/sdiff-no-kill.patch | 32 --- > .../diffutils/diffutils_3.6.bbappend | 18 --- > .../diffutils/diffutils_3.7.bbappend | 14 Should this be called simply

[yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7

2019-02-20 Thread Joshua Watt
Upgrade diffutils from 3.6 to 3.7. The upstream made several fixes so the local patches are no longer necessary, but the gnulib-tests need to be dropped since they do not compile properly Signed-off-by: Joshua Watt --- .../diffutils/diffutils/sdiff-no-kill.patch | 32 ---

[yocto] Problems using MIRRORS variables

2019-02-20 Thread Ryan Harkin
Hello, I'm having a few problems when using the MIRRORS variable for GIT repos. I see the same problems with the PREMIRRORS variable. My use-case is: 1. company A has a private layer with SRC_URI that points to private git 2. company A needs to share layers with company B 3. company B cannot

Re: [yocto] Add new compiler macro

2019-02-20 Thread Khem Raj
On Wed, Feb 20, 2019 at 12:42 AM wrote: > Hi, > > i tried to add CFLAGS += "-MMC_WRITE" > (i dont know if -DMMC_WRITE was a typo or not and tryed both) > -D is right way to pass defines it seems your makefiles are ignoring cflags so you might have to fix that > > > i dont get any error but in

[yocto] icecast error

2019-02-20 Thread Leonardo Jose Duarte MendesJunior
Good morning. I'm trying to compile the icecast, and I had this issue: Initialising tasks: 100% |#| Time: 0:00:03 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR:

Re: [yocto] Add cmd.py library for python-core package

2019-02-20 Thread Piotr Piwko
śr., 20 lut 2019 o 12:30 Alexander Kanavin napisał(a): > > On Wed, 20 Feb 2019 at 12:25, Piotr Piwko wrote: > > I would like to add cmd.py library to my final image. In order to do > > so I modified python2-manifest.json file from poky delivery. > I'm not sure why you had to modify the manifest,

Re: [yocto] Add cmd.py library for python-core package

2019-02-20 Thread Alexander Kanavin
On Wed, 20 Feb 2019 at 12:25, Piotr Piwko wrote: > I would like to add cmd.py library to my final image. In order to do > so I modified python2-manifest.json file from poky delivery. > > This solution works fine. However, is there any possibility to do not > change the global

[yocto] Add cmd.py library for python-core package

2019-02-20 Thread Piotr Piwko
Hi, I would like to add cmd.py library to my final image. In order to do so I modified python2-manifest.json file from poky delivery. This solution works fine. However, is there any possibility to do not change the global poky/python2-manifest,json file and get the same result? I would like to

Re: [yocto] Add new compiler macro

2019-02-20 Thread luciosantinell
Hi, i tried to add CFLAGS += "-MMC_WRITE" (i dont know if -DMMC_WRITE was a typo or not and tryed both) i dont get any error but in my recipes the code wrapped in #ifdef MMC_WRITE #endif is not compiled... i even tried to add a sintax error between the ifdef so, if compiler see MMC_WRITE