[yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

Display blacklisted information for recipes on Layerindex, in the recipe details, as well as the recipe search page, and layer page tables. This information is pulled from the PNBLACKLIST variable. Includes a hover text containing the reason for blacklist labels. Changes to Django and Layerindex

[yocto] [eclipse-poky][PATCH] OptionsPage.java: Allow BC Project name to be other than poky folder

Fixes [Yocto 8407] This change allows a new Yocto Project Bitbake Commander project to be named as desired, not as the poky folder. Signed-off-by: Jose Lamego --- .../src/org/yocto/bc/ui/wizards/install/OptionsPage.java | 12 1 file changed, 4

Re: [yocto] RFC: Reference updater filesystem

Hi, Hey Jen, I was looking for an image upgrade solution and factory reset solution using overlayfs. The idea have two partitions one read-only with the factory image, other to hold the changes that were made by time. The factory reset feature should be triggered by a hided button that can be

Re: [yocto] RFC: Reference updater filesystem

> Am 23.11.2015 um 22:15 schrieb Mariano Lopez : > > There has been interest in an image based software updater in Yocto Project. > The proposed solution for a image based updater is to use Stefano Babic's > software updater (http://sbabic.github.io/swupdate). This

[yocto] [PATCH 7/8] [meta-mingw] [jethro/master] toolchain-scripts-mingw32.bbclass: Update to match YP 2.0 release

The environment script generatation is updated to match YP 2.0 version. In addition, there was an error in the way the EXTRAPATH component was being generated. Signed-off-by: Mark Hatle --- classes/toolchain-scripts-mingw32.bbclass | 24 +++- 1

[yocto] [PATCH 0/8] [meta-mingw] [jethro/master] Update to YP 2.0

The first 6 of the patches referenced in this summary have previous been sent to the Yocto Project mailing list. I will only be sending patches 7 and 8 as they are new. They entire patch set can be inspected at: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mgh/meta-mingw or

[yocto] [PATCH 8/8] [meta-mingw] [jethro/master] gcc-cross-canadian: Workaround LTO failure

Workaround for the failure: e:/windri~1/lx8.sdk/qemux8~1.800/sysroots/i686-w~1/usr/bin/i586-w~3/../../libexec/i586-wrs-linux/gcc/i586-wrs-linux/5.2.0/real-ld.exe: unrecognized option '-plugin' This disables the LTO support in the compiler, but does allow things to compile and link properly.

[yocto] Yocto Project Status WW48

Current Dev Position: YP 2.1 M1 Next Deadline: YP 2.1 M1 Cutoff December 7, 2015 noon GMT SWAT team rotation: Alejandro -> Maxim https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * Note that M1 is drawing near, time flies! * YP 2.1

Re: [yocto] RFC: Reference updater filesystem

2015-11-30 16:20 GMT-02:00 Jens Rehsack : >> 2015-11-30 14:10 GMT-02:00 Jens Rehsack : >>> Am 23.11.2015 um 22:15 schrieb Mariano Lopez : There has been interest in an image based software updater in Yocto Project.

Re: [yocto] RFC: Reference updater filesystem

On 23.11.2015 22:15, Mariano Lopez wrote: > There has been interest in an image based software updater in Yocto > Project. The proposed solution for a image based updater is to use > Stefano Babic's software updater (http://sbabic.github.io/swupdate). > This software do a binary copy, so it is

Re: [yocto] Cross-compiling python fails with new custom tuning

Mark, I am continuing to look at this. I hope you don't mind if I keep updating this thread with my investigation. First, I figured out my confusion. I was associating the wrong Makefile command with the illegal instruction. It was actually the command under the recipe for 'sharedmods', but it

Re: [yocto] RFC: Reference updater filesystem

> 2015-11-30 14:10 GMT-02:00 Jens Rehsack : >> >>> Am 23.11.2015 um 22:15 schrieb Mariano Lopez : >>> >>> There has been interest in an image based software updater in Yocto >>> Project. The proposed solution for a image based updater is to use

[yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

Hi, I have one kernel tree where I keep all my modules in-tree. Inside kernel I have two FOO_defconfig and BAR_defconfig which are configurations for FOO-board and BAR-board. On Yocto I have core-layer, FOO-bsp layer and BAR-bsp layer. At core-layer I have linux-custom.bb file which has the URI

Re: [yocto] Kernel header generation

On Nov 27, 2015 5:48 AM, "Sarayu Krishna Sivanandam" wrote: > > Hi , > > I have written a kernel module which i am currently building along with the yocto kernel but i want to be able to move my code to a different repository and be able to build it as a stand alone module. >

Re: [yocto] Problem using unix source in do_compile

On Nov 25, 2015 7:30 PM, "Edward Vidal" wrote: > > Hello all, > After a long time of trying to get Michael Looijmans fpga-image-adi.bb from meta-topic to work. I wanted to share the fix. I was running Ubuntu 12.04. > which sh > /bin/sh > cd /bin > ls -la sh > lrwxrwxrwx

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

Hi Alex, On Mon, 30 Nov 2015 16:03:05 Alex Franco wrote: > Display blacklisted information for recipes on Layerindex, in the > recipe details, as well as the recipe search page, and layer page > tables. This information is pulled from the PNBLACKLIST variable. > Includes a hover text containing

Re: [yocto] [PATCH][yocto-kernel-cache] netfilter: enable several netfilter options

On 2015年11月30日 13:22, Bruce Ashfield wrote: On 2015-11-26 12:25 AM, rongqing...@windriver.com wrote: From: Roy Li the below kernel options are enabled: LOG target support IPv6 connection tracking support, "addrtype" address type match support

Re: [yocto] strange QA issue - how to ignore automatic so dependency

> On Nov 30, 2015, at 3:15 PM, Dvorkin Dmitry wrote: > > I know. But > it really does not require to have libX* in the system to successfully run > JDK+our software > We're using simple tar xvzf jdk-...tar.gz in all of our embedded systems, so > I know what I'm talking

Re: [yocto] Cross-compiling python fails with new custom tuning

This is the patch that we ended up using: http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113457.html http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113456.html http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113458.html

[yocto] strange QA issue - how to ignore automatic so dependency

I'm trying to include binary JDK into my linux image. just unpacking jdk-...tar.gz into recipe image and packing it into RPM (I'm using RPM as base of my distribution). after adding INSANE_SKIP_${PN} = "file-rdeps ldflags dev-so build-deps" into recipe I've got no errors or warning while

Re: [yocto] strange QA issue - how to ignore automatic so dependency

I know. But it really does not require to have libX* in the system to successfully run JDK+our software We're using simple tar xvzf jdk-...tar.gz in all of our embedded systems, so I know what I'm talking about, sorry. This feature blocks my efforts to have a well-designed system with

Re: [yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

On Mon, 2015-11-30 at 17:25 -0200, Daniel. wrote: > Hi, > > I have one kernel tree where I keep all my modules in-tree. Inside > kernel I have two FOO_defconfig and BAR_defconfig which are > configurations for FOO-board and BAR-board. On Yocto I have > core-layer, FOO-bsp layer and BAR-bsp layer.

Re: [yocto] strange QA issue - how to ignore automatic so dependency

> On Nov 30, 2015, at 2:42 PM, Dvorkin Dmitry wrote: > > > I'm trying to include binary JDK into my linux image. > just unpacking jdk-...tar.gz into recipe image and packing it into RPM (I'm > using RPM as base of my distribution). > > after adding > INSANE_SKIP_${PN} =

Re: [yocto] Cross-compiling python fails with new custom tuning

OK I've dug into this further today, and here are some findings: With my patch (which is similar to yours), it fails do_compile/package_qa because of poisoned system directories during the compilation steps. This approach seems to be a bust. Originally when I tested it, I hacked up the Makefile

Re: [yocto] Cross-compiling python fails with new custom tuning

Mark, great! I was literally about to try double-stacking the PATH next (since removing both didn't work for reasons that became obvious after running the experiment), so that it would grab the *.so's from python-native and then the sysconfig from the python-cross. Looks like I may need to

Re: [yocto] strange QA issue - how to ignore automatic so dependency

On 01.12.2015 02:22, Khem Raj wrote: On Nov 30, 2015, at 3:15 PM, Dvorkin Dmitry wrote: I know. But it really does not require to have libX* in the system to successfully run JDK+our software We're using simple tar xvzf jdk-...tar.gz in all of our embedded systems, so I

[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Dec. 1, 2015 8:00 AM US Pacific Time

Tuesday, Dec. 1, 2015 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule

Re: [yocto] [PATCH][yocto-kernel-cache] netfilter: enable several netfilter options

On 2015-11-30 8:08 PM, Rongqing Li wrote: On 2015年11月30日 13:22, Bruce Ashfield wrote: On 2015-11-26 12:25 AM, rongqing...@windriver.com wrote: From: Roy Li the below kernel options are enabled: LOG target support IPv6 connection tracking support,

Re: [yocto] Kernel header generation

Hi Khem . Thanks for your response. But i am not sure if i understand clearly. My intention here is to generate kernel headers and i wanted to understand how to do the same . Based on some online reference , I tried to add the lines ( IMAGE_INSTALL_append = " kernel-devsrc"

[yocto] [prelink-cross] Prelinking to wrong library ld-linux.so.3 instead ld-linux-armhf.so.3

Hi, As the subject states, I'm having that problem with Yocto. I'm using Yocto 1.7 and already updated the prelink-cross to latest version. This happens only on the applications I've added myself. The actual Yocto applications compiles just fine. I don't have any autoconf in use with my

Re: [yocto] Question about configure.ac:46: error: possibly undefined macro

On 28 November 2015 at 01:32, Li, Hao H wrote: > autoreconf: running: > /home/ssg/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf > --include=/home/ssg/yocto/poky/build/tmp/work/corei7-64-smallos-linux/libmicrohttpd/0.9.43-r0/libmicrohttpd-0.9.43/m4/ > --force > >

Re: [yocto] [meta-raspberrypi][PATCH v3 0/2] Add support for 4.2 kernel with vc4 DRM/KMS driver

On 11/20/2015 02:30 PM, Andreas Müller wrote: > On Fri, Nov 20, 2015 at 5:09 PM, Khem Raj wrote: >> On Fri, Nov 20, 2015 at 7:34 AM, Javier Martinez Canillas >> wrote: >>> On 11/10/2015 11:45 AM, Javier Martinez Canillas wrote: Hello Andrei,

Re: [yocto] [meta-raspberrypi][PATCH v3 0/2] Add support for 4.2 kernel with vc4 DRM/KMS driver

On Mon, Nov 30, 2015 at 1:08 PM, Javier Martinez Canillas wrote: > On 11/20/2015 02:30 PM, Andreas Müller wrote: >> On Fri, Nov 20, 2015 at 5:09 PM, Khem Raj wrote: >>> On Fri, Nov 20, 2015 at 7:34 AM, Javier Martinez Canillas >>>