Re: [yocto] [EXTERNAL] Re: Openjdk-8 fetcher failure

HI John, Using the 'wget', I am able to download the file. Best Regards Alok Pawar Sr. Engineer Product Development -Original Message- From: Maxin B. John [mailto:maxin.j...@intel.com] Sent: Monday, June 19, 2017 6:37 PM To: Pawar, Alok Cc:

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

did I put it wrongly ? === Loading cache: 100% |#| Time: 0:00:01 Loaded 2794 entries from dependency cache. ERROR: ParseError at

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

drwxrwxr-x 5 bianchi77 bianchi77 4.0K Jun 14 14:31 . drwxrwxr-x 3 bianchi77 bianchi77 4.0K Jun 12 15:50 .. drwxrwxr-x 2 bianchi77 bianchi77 4.0K Jun 12 15:50 cef3 -rw-rw-r-- 1 bianchi77 bianchi77 2.7K Jun 12 15:50 cef3_280796.bb drwxrwxr-x 4 bianchi77 bianchi77 4.0K Jun 12 15:50 chromium

Re: [yocto] Some Arch Linux build fixes

On Tue, Jun 20, 2017 at 10:09 AM, Anton Novikov wrote: > Hi, and all have a nice day. > > > My company contributes to OpenBMC project, whose code has an > 'import-layers/yocto-poky' > > git subtree. I'm trying to build it on Arch Linux, which is a rolling > release

Re: [yocto] RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?

I got those messages : === musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (89,

Re: [yocto] RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?

On Tue, Jun 20, 2017 at 9:52 PM, Riko Ho wrote: > How can I obtain that "udev" ? and where can I find the log ? "dmesg" | > "grep" ? > > Two days ago, I saw activity on UART when the dongle was inserted, but it's > gone now, I can't see the activity.. > Any clues ? dmesg

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

add it to chromium recipe itself if you dont have a bbappend for it. On Tue, Jun 20, 2017 at 9:53 PM, Riko Ho wrote: > Ok, thanks a lot for the parameter idea, where will I put that ? local.conf, > bblayers.conf ? > > > On 20/06/17 13:08, Khem Raj wrote: > > On Mon, Jun

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

Ok, thanks a lot for the parameter idea, where will I put that ? local.conf, bblayers.conf ? On 20/06/17 13:08, Khem Raj wrote: On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho wrote: My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can help ? add

Re: [yocto] RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ?

How can I obtain that "udev" ? and where can I find the log ? "dmesg" | "grep" ? Two days ago, I saw activity on UART when the dongle was inserted, but it's gone now, I can't see the activity.. Any clues ? Thanks On 20/06/17 12:51, Khem Raj wrote: On Mon, Jun 19, 2017 at 8:46 PM, Riko Ho

Re: [yocto] [yocto-docs][PATCH v2] ref-manual: Replace uclibc to musl

Thanks. I confirmed it. Changhyeok 2017-06-21 9:24 GMT+09:00 Kristi Rifenbark : > Changhyeok, > > Fix is backported to morty (2.2.2) - http://git.yoctoproject.org/ > cgit/cgit.cgi/yocto-docs/commit/?h=morty=e131c26ee1ab268679f7762dbe2676 > 0bd859e0e5 > > Fix is

[linux-yocto] [kernel-cache][PATCH 1/1] pwm_leafhill: set pwm as built in by default

From: "Chai, Chong Yi" DC-IRIS camera driver has dependecy on PWM driver. This camera driver is built in and require PWM driver to be built in as well. Signed-off-by: Chai, Chong Yi --- bsp/leafhill/pwm_leafhill.cfg | 4

[linux-yocto] [kernel-cache][PATCH 0/1] Update PWM config for leafhill platform

From: "Chai, Chong Yi" Hi Bruce, This patch is targeted for yocto-kernel-cache yocto-4.1 branch. The changes on configs enable PWM to be built in driver rather than kernel module which is require by DC-IRIS camera driver. The config is separated from main leafhill

Re: [yocto] [prelink-cross][PATCH] src/rtld: Add MicroBlaze support based on glibc-2.24

Ok, I've verify this is working properly (not on MicroBlaze, but on other architectures). One observation, recent gcc appears to have changed something in CXX (at least on x86-64), and I'm now getting: ../src/prelink: /home/root/prelink-cross/testsuite/cxx1: COPY relocations don't point into

[yocto] Yocto eSDK, Editing/Adding Recipes, and VCS

I've been trying to document some workflows for my developers using the Yocto eSDK for our image, but I am coming up empty when it comes to editing or adding recipes. I can use devtool to edit a recipe like so: devtool edit-recipe -a my-recipe But any changes I make are hidden away in the

Re: [yocto] patch files

Sorry. I'm doing 5 things at once here. I am fetching a source RPM inside a simple RECIPE. > On June 20, 2017 at 1:33 PM RUSSELL PETERSON wrote: > > > Hello, > > > I am fetching a src RPM file inside a simple library. The RPM basically > contains a tar

[yocto] patch files

Hello, I am fetching a src RPM file inside a simple library. The RPM basically contains a tar file with the source and 2 patch files. How to I apply those patch files? If I put them in the SRC_URI the fetch fails. Is there a way I can add them to some list that do_patche uses or do

Re: [yocto] [yocto-docs][PATCH v2] ref-manual: Replace uclibc to musl

Hi Scott, Kristi Could review my changes? Thanks Changhyeok 2017-06-12 14:52 GMT+09:00 Changhyeok Bae : > This patch should be merged in morty (2.2), pryo (2.3), and master branch. > > Thanks > Changhyeok > > 2017-06-12 13:07 GMT+09:00 Changhyeok Bae

[yocto] Minimal eSDK with PKGDATA causes licensing issues

I added these lines to my eSDK image I'm trying to build: SDK_EXT_TYPE = "minimal" SDK_INCLUDE_TOOLCHAIN = "1" SDK_INCLUDE_PKGDATA = "1" But bitbake comes back with lots of license issues (mpv, gstreamer, libvdpau, etc). These are all the commercial licensed recipes. I don't want PKGDATA for

[yocto] Some Arch Linux build fixes

Hi, and all have a nice day. My company contributes to OpenBMC project, whose code has an 'import-layers/yocto-poky' git subtree. I'm trying to build it on Arch Linux, which is a rolling release distribution, and has pretty recent package versions, which triggers some bugs, which I'm

[yocto] AppArmor

Hi, Has anyone tried using AppArmor with Yocto? The recipe in the meta-security layer is broken, and when fixed so it actually builds, it turns out the installed init script relies on functions not found in Yocto's version of LSB. Regards, Anders --

Re: [yocto] [prelink-cross][PATCH] src/rtld: Add MicroBlaze support based on glibc-2.24

On 6/20/17 7:08 AM, Nathan Rossi wrote: > On 20 June 2017 at 00:20, Mark Hatle wrote: >> I've merged this to the cross_prelink_staging (and master_staging, even >> though >> it's a no-op there). The change seems fairly obvious to me. >> >> Can you verify it is working

Re: [yocto] [prelink-cross][PATCH] src/rtld: Add MicroBlaze support based on glibc-2.24

On 20 June 2017 at 00:20, Mark Hatle wrote: > I've merged this to the cross_prelink_staging (and master_staging, even though > it's a no-op there). The change seems fairly obvious to me. > > Can you verify it is working properly as merged into cross_prelink_staging, >

[yocto] Errors while building imx6qsabresd using fsl-community-bsp repo

Hi, I am new to yocto training and I am trying to build a linux for imx series target from NXP. I got the bsp layer along with poky using the following: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b daisy repo sync Now when I try to build core-image-minimal I get the

Re: [yocto] [meta-raspberrypi] Configure eth0 to come up with Link-Local IPv6 address only

I was unable to get the Raspberry Pi 3 I am targeting to start with eth0 up and only an IPv6 link local address present on eth0, using only a /etc/network/interfaces file. In the end I added shell script under /etc/rc5.d which called out to `ifconfig eth0 up`. This brought eth0 up with only a

Re: [yocto] useradd and one sysroot per recipe in pyro

Hi Laurent, > In pyro the creation of users and group (using the useradd class) is done > during > the package pre-installation. > > So my best guess is that you could move the owner/group change in the package > post-installation as follows: thanks for your advice. Currently it seems - as

Re: [yocto] useradd and one sysroot per recipe in pyro

Hi Maxin, > > Do I have to add shadow-native in all these recipes or is it a bug / > > regression in > pyro? > > It is one of those "known" limitations which fell through the cracks. > https://bugzilla.yoctoproject.org/show_bug.cgi?id=8078 > > Thanks for bringing this up. We need to address