Re: [yocto] Running Docker

2018-02-28 Thread Khem Raj
On 2/28/18 2:05 AM, Jakob Hasse wrote: > Hello Bruce, > > I kind of fixed the problem by creating a link with the name of the > interpreter which the docker executable expects, pointing to the normal > /lib/ld-linux-armhf.so.3 interpreter. After that, docker would run. > you might be better

[linux-yocto] [PATCH] aufs: fix compile warning

2018-02-28 Thread Dengke Du
From: "Kexin(Casey) Chen" Forward port linux-yocto-4.8's patch to fix the build warning. http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.8/commit/?h=standard/base=7e0dd2f2b0971f0e3191e1ddc088e09eb9855567 fs/aufs/debug.h:95:19: warning: comparison of

[linux-yocto] v4.8.x - stable updates comprising v4.8.27

2018-02-28 Thread Paul Gortmaker
Bruce, Yocto kernel folks: Here is another 4.8.x stable update. Continuing on top of the previously released v4.8.26 kernel, we now have content selected from the 4.9.x series to address some of the high profile CVEs that have garnered a lot of attention this year. One departure of note, is

Re: [yocto] Adding Gnome to X11

2018-02-28 Thread Burton, Ross
Because by doing IMAGE_INSTALL += you wiped out the default value which is a ?=. gnome-desktop3 isn't the GNOME interface though, it's just a small library. If you want the full GNOME 3 desktop then you'll need to start with meta-gnome and write more recipes, as it's not entirely packaged. Ross

Re: [yocto] [Yocto][Meta-Raspberrypi] Yocto apt sources.list for Raspberry Pi

2018-02-28 Thread Alexander Kanavin
On 02/26/2018 04:14 PM, Laigui Qin wrote: I would like to think there is a well maintained Yocto/Poky repository somewhere in the world like the debian/Raspbian deb source to leverage (build and maintain my own repo is not my purpose.) Looks like there is not such repo available... Please

[yocto] [auh][PATCH] weeklyjob.sh: also clean up the workspace source directory

2018-02-28 Thread Alexander Kanavin
As devtool does not always remove it. Signed-off-by: Alexander Kanavin --- weeklyjob.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/weeklyjob.sh b/weeklyjob.sh index 2e8c434..412685e 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -24,6 +24,7 @@

Re: [yocto] Changing the tty/UART of busybox

2018-02-28 Thread Jakob Hasse
Hi Maxin, thanks, this worked! All the Best, Jakob On 28.02.2018 14:13, Maxin B. John wrote: Hi Jakob, On Wed, Feb 28, 2018 at 11:15:42AM +0100, Jakob Hasse wrote: Hello, we need to change the tty on which busybox is sitting. Right now I could change the UART for the kernel and all

[yocto] Adding Gnome to X11

2018-02-28 Thread Q . Gouès
Hi, I am trying to add gnome to my x11 image based on the recipe core-image-x11. I am using Poky 2.0 (Jethro). For that, I added the following line to my recipe: /IMAGE_INSTALL += "gnome-desktop3"/ Unfortunately I get the following error: /switch_root: can't execute '/sbin/init': No such

[yocto] [auh][PATCH] upgradehelper.py: fix arguments to _pkg_upgradable()

2018-02-28 Thread Alexander Kanavin
Maintainer whitelisting was broken, in particular. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index b22b915..169e9ce 100755 ---

Re: [yocto] Changing the tty/UART of busybox

2018-02-28 Thread Maxin B. John
Hi Jakob, >On Wed, Feb 28, 2018 at 11:15:42AM +0100, Jakob Hasse wrote: > >Hello, > >we need to change the tty on which busybox is sitting. Right now I could change > the UART for the kernel and all program output after the boot to our favorite > UART (via kernel cmd line). But the login promt

[yocto] Changing the tty/UART of busybox

2018-02-28 Thread Jakob Hasse
Hello, we need to change the tty on which busybox is sitting. Right now I could change the UART for the kernel and all program output after the boot to our favorite UART (via kernel cmd line). But the login promt and all interaction with the device is still on the old UART. So I guess it's a

Re: [yocto] Running Docker

2018-02-28 Thread Jakob Hasse
Hello Bruce, I kind of fixed the problem by creating a link with the name of the interpreter which the docker executable expects, pointing to the normal /lib/ld-linux-armhf.so.3 interpreter. After that, docker would run. All the Best, Jakob On 06.02.2018 02:15, Bruce Ashfield wrote: On