Re: [yocto] esdk without using Poky?

On Wed, 02 Nov 2016 03:02:11 Gary Thomas wrote: > On 2016-11-02 02:44, Paul Eggleton wrote: > > On Wed, 02 Nov 2016 02:37:57 Gary Thomas wrote: > >> On 2016-11-01 21:33, Paul Eggleton wrote: > >>> On Tue, 01 Nov 2016 13:36:57 Gary Thomas wrote: > On 2016-10-31 23:06, Paul Eggleton wrote: >

Re: [yocto] esdk without using Poky?

On 2016-11-02 02:44, Paul Eggleton wrote: On Wed, 02 Nov 2016 02:37:57 Gary Thomas wrote: On 2016-11-01 21:33, Paul Eggleton wrote: On Tue, 01 Nov 2016 13:36:57 Gary Thomas wrote: On 2016-10-31 23:06, Paul Eggleton wrote: FYI the eSDK will use whatever you set in DISTRO - you have your own

Re: [yocto] esdk without using Poky?

On Wed, 02 Nov 2016 02:37:57 Gary Thomas wrote: > On 2016-11-01 21:33, Paul Eggleton wrote: > > On Tue, 01 Nov 2016 13:36:57 Gary Thomas wrote: > >> On 2016-10-31 23:06, Paul Eggleton wrote: > >>> FYI the eSDK will use whatever you set in DISTRO - you have your own > >>> distribution, but I assume

Re: [yocto] esdk without using Poky?

On 2016-11-01 21:33, Paul Eggleton wrote: On Tue, 01 Nov 2016 13:36:57 Gary Thomas wrote: On 2016-10-31 23:06, Paul Eggleton wrote: FYI the eSDK will use whatever you set in DISTRO - you have your own distribution, but I assume you are still referencing poky - perhaps as an include from your

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

> On Nov 1, 2016, at 4:22 PM, Burton, Ross wrote: > > > On 1 November 2016 at 22:20, Daniel. > wrote: > Just as a note, I've been using archlinux for about a year and have never > faced "distro related problems",

Re: [yocto] meta-mingw

On 11/1/16 5:58 PM, Bystricky, Juro wrote: > Most likely the error is caused by the change from TARGET_ARCH -> SDK_SYS > Try this: > https://lists.yoctoproject.org/pipermail/yocto/2016-October/032306.html Thank you. This does in fact fix the problem. --Mark >> -Original Message- >>

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On 1 November 2016 at 22:20, Daniel. wrote: > Just as a note, I've been using archlinux for about a year and have never > faced "distro related problems", except when the gcc6 comes out. Anyway I'm > using daisy in my work. I think that making old releases supported by X >

Re: [yocto] meta-mingw

Most likely the error is caused by the change from TARGET_ARCH -> SDK_SYS Try this: https://lists.yoctoproject.org/pipermail/yocto/2016-October/032306.html > -Original Message- > From: Mark Hatle [mailto:mark.ha...@windriver.com] > Sent: Tuesday, November 1, 2016 3:41 PM > To: Yocto

Re: [yocto] meta-mingw

I sent a set of patches a while ago for meta-mingw/master branch. "krogoth" and "morty/master" need separate branches. "krogoth" branch exists, but I think morty branch needs to be created yet. > -Original Message- > From: Mark Hatle [mailto:mark.ha...@windriver.com] > Sent: Tuesday,

[yocto] meta-mingw

I was trying to build meta-mingw (master) with oe-core (morty). I'm getting a failure: | ERROR: Function failed: do_configure (log file is located at .../nativesdk-mingw-w64-runtime/3.1.0-r0/temp/log.do_configure.208815) ERROR: Task

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

Just as a note, I've been using archlinux for about a year and have never faced "distro related problems", except when the gcc6 comes out. Anyway I'm using daisy in my work. I think that making old releases supported by X distro doesn't make any sense... Cheers, 2016-11-01 19:36 GMT-02:00 Bas

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On 01/11/16 18:11, Burton, Ross wrote: On 1 November 2016 at 17:05, Bas Mevissen > wrote: What are the criteria to call a distro supported? The short version is that it's a distro that doesn't change too much, is still supported, and we

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On Tue, 01 Nov 2016 17:11:21 Burton, Ross wrote: > On 1 November 2016 at 17:05, Bas Mevissen wrote: > > What are the criteria to call a distro supported? > > The short version is that it's a distro that doesn't change too much, is > still supported, and we have builders on

Re: [yocto] esdk without using Poky?

On Tue, 01 Nov 2016 13:36:57 Gary Thomas wrote: > On 2016-10-31 23:06, Paul Eggleton wrote: > > FYI the eSDK will use whatever you set in DISTRO - you have your own > > distribution, but I assume you are still referencing poky - perhaps as an > > include from your distro configuration? At least

Re: [yocto] how to copy a tar file to Root file system

I have an example of a recipe exploding a tar here: https://gist.github.com/gkos/02eccb8e1e02312327aa6db6cdc9d501 The tar is used as a source. So the bitbake explodes it to ${WORKDIR} and I simply copy it to /opt I hope that this helps :) Regards, 2016-11-01 18:00 GMT-02:00 Paul Eggleton

Re: [yocto] how to copy a tar file to Root file system

On Tue, 01 Nov 2016 18:45:02 swapna.gurum...@microchip.com wrote: > Every step I take close, I take 2 back :( > My bb now looks like the one attached. I had to add each folder for > FILES_${PN} contrary to your advice otherwise I got the following error: > ERROR: crank-1.0-r2 do_package: QA Issue:

[yocto] [ANNOUNCEMENT] Yocto Project 2.2 (morty 16.0.0) Released

Hello, The latest release of the Yocto Project 2.2 (morty-16.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.2/poky-morty-16.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.2/poky-morty-16.0.0.tar.bz2 A gpg signed version of these

Re: [yocto] [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration

Hi Paul, Thanks for your feedback. Unfortunately I was suspecting such a problem. Regarding the config below, is it possible to install the "dispmanx"component to activate EGL ? What recipe provides dispmanx ? Karim De : Paul Barker

Re: [yocto] how to copy a tar file to Root file system

Hello, Every step I take close, I take 2 back :( My bb now looks like the one attached. I had to add each folder for FILES_${PN} contrary to your advice otherwise I got the following error: ERROR: crank-1.0-r2 do_package: QA Issue: crank: Files/directories were installed but not shipped in any

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On 1 November 2016 at 17:05, Bas Mevissen wrote: > What are the criteria to call a distro supported? > The short version is that it's a distro that doesn't change too much, is still supported, and we have builders on autobuilder.yoctoproject.org running that distro. The

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On 01/11/16 16:27, Burton, Ross wrote: That's a mistake, I consider the whitelist assignment in poky.conf to be canonical and that includes 16.04. What are the criteria to call a distro supported? Scott, can you update the list at

[yocto] archiver.bbclass raising exception

Hi I switched from yocto 2.0.1 to yocto 2.1.1 and use the archiver class with the following settings: INHERIT += "archiver" ARCHIVER_MODE[src] = "original" ARCHIVER_MODE[recipe] = "1" I'm getting this exception: ERROR: dbus-c++-native-0.9.0-r8 do_ar_recipe: Error executing a python function

[yocto] [meta-security][PATCH] suricata: update package to 3.1.3

*Changes* Bug #1861: Suricata with multi tenancy does not start in 3.1/3.1.1 Bug #1889: Suricata doesn't error on missing semicolon Bug #1910: libhtp 0.5.23 (3.1.x) Bug #1912: http.memcap reached condition can lead to dead lock Bug #1913: af-packet fanout detection broken on Debian Jessie Bug

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

Thank you for the quick answer MV From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: November 01, 2016 11:28 To: Vuille, Martin (Martin); Rifenbark, Scott M Cc: yocto@yoctoproject.org Subject: Re: [yocto] Yocto 2.2 Morty supported Linux Distros On 1 November 2016 at 15:19, Vuille, Martin

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On 1 November 2016 at 15:19, Vuille, Martin (Martin) wrote: > Is that correct/intentional, or a documentation oversight? > > Ubuntu 16.04 is mentioned elsewhere in the docs. > > That's a mistake, I consider the whitelist assignment in poky.conf to be canonical and that

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

Hi Martin, I would be surprised if it isn't. I've been running meta-openembedded and openembedded-core in our project without any issues on 16.04 with both Krogoth and Morty. Would be good if the project team can confirm though. Herman On 2016-11-01 16:19, Vuille, Martin (Martin) wrote:

[yocto] Yocto 2.2 Morty supported Linux Distros

Noticed that Ubuntu 16.04 LTS is not on the list of supported distributions for Morty. Is that correct/intentional, or a documentation oversight? Ubuntu 16.04 is mentioned elsewhere in the docs. We are planning to upgrade from Ubuntu 12.04 LTS and it would make more sense to go to the latest LTS

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Nov. 1, 2016 8:00 AM US Pacific Time

Attendees: Armin, Ross, Stephen, Mark, Randy, Richard, Saul, Agenda: * Opens collection - 5 min (Stephen) Discussed list of contributors to oe-core Management List * Yocto Project status - 5 min (Stephen/team) *YP 2.2 is getting ready for release. It should release in the next

[yocto] Question about wic partition creation

We are using Yocto (jethro and krogoth) to build an image for a device. I organized the compilation process into multiple stages for easier integration with our tooling. The last stage is a call to `wic` to create a drive image that we can then `dd` to a real drive to get a workable system.

[yocto] [meta-raspberrypi][PATCH] u-boot: Fix appending to RDEPENDS

The += operator should not be used in combination with overrides as it will clear any existing values in the variable. Example: FOO = "bar" FOO_rpi += "baz" The above example would result in FOO being equal to " baz" instead of "bar baz". The bbappend is changed to use a wildcard instead of a

[yocto] [meta-raspberrypi][PATCH] u-boot: Simplify boot script

device_tree_address=0x100 is set in config.txt so the firmware will load a patched device tree blob to 0x100 before passing control to U-Boot. The U-Boot script will then read the command line arguments generated by the firmware from the device tree and boot the kernel with the command line

Re: [yocto] why do some openstack layer.conf files add classes to BBFILES?

On Tue, 1 Nov 2016, Christopher Larson wrote: > > On Tue, Nov 1, 2016 at 1:57 AM, Robert P. J. Day > wrote: >   just noticed the following property for a bunch of the openstack > layers at: > >

Re: [yocto] why do some openstack layer.conf files add classes to BBFILES?

On Tue, Nov 1, 2016 at 1:57 AM, Robert P. J. Day wrote: > just noticed the following property for a bunch of the openstack > layers at: > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/ > > some of the layer.conf files contain the line: > > BBFILES

Re: [yocto] esdk without using Poky?

On 2016-10-31 23:06, Paul Eggleton wrote: Hi Gary, On Mon, 31 Oct 2016 13:19:18 Gary Thomas wrote: I'm trying to build an extensible SDK (eSDK) for my target and running into a few problems. gthomas@zeus:~$ /work/tmp/mlb-glibc-x86_64-arm-toolchain-ext-2.2+snapshot.sh MLB @SDK_TITLE@

Re: [yocto] how to copy a tar file to Root file system

On 01/11/16 05:03, swapna.gurum...@microchip.com wrote: With the attached recipe I get the following error: From the recipe: inherit pkgconfig Why do you inherit pkgconfig and aren't you inheriting bin_package? Regards, Bas. -- Bas. -- ___

[yocto] why do some openstack layer.conf files add classes to BBFILES?

just noticed the following property for a bunch of the openstack layers at: http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/ some of the layer.conf files contain the line: BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend

Re: [yocto] how to copy a tar file to Root file system

On Tue, 01 Nov 2016 04:03:58 swapna.gurum...@microchip.com wrote: > With the attached recipe I get the following error: > ERROR: crank-1.0-r0 do_package: QA Issue: crank: Files/directories were > installed but not shipped in any package: /opt > /opt/sb_launch.sh > /opt/clear_buffers >