Re: [yocto] qemu and grub

On Tue, 2018-10-30 at 22:14 +0100, Dimitris Tassopoulos wrote: > Hi all. > > Usually I have a small x86_64 board that I test images. But for the > first > time I've tried to use yocto to do some development on grub. I've > used > qemu to do grub development before and I know that this works fine.

Re: [yocto] 2.6 migration guide

Paul, Thanks for sending. Contributors I have an initial section at https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release, which is based on Richard's input. I am sure there are more items. Thanks, Scott On Tue, Oct 23, 2018 at 2:14 PM Paul

Re: [yocto] Yocto and Debian package repositories

On Tue, Oct 30, 2018 at 8:14 AM Mauro Ziliani wrote: > > Hi all. > > I often work with Debian and I build my own repository accessible with apt. > > I look that when I build the image recipe many deb pacakages are > produced with Packages and Release ready. > > How can I use this pakcages to

[yocto] qemu and grub

Hi all. Usually I have a small x86_64 board that I test images. But for the first time I've tried to use yocto to do some development on grub. I've used qemu to do grub development before and I know that this works fine. I just use grub-mkrescue to create images with my grub script and then boot.

Re: [yocto] Moving to Yocto 2.3 - recipe-specific sysroots - improving the documentation

On Tue, Oct 30, 2018 at 1:06 AM CHMIELARZ Radoslaw wrote: > > Hi all, > > > > I think the documentation on migrating between Yocto 2.2 and 2.3 needs more > clarification as to how did the sysroots have changed. > > > > I wanted to migrate our build system from 2.2 to 2.5 and one package in >

Re: [yocto] busybox build failure

On Tue, Oct 30, 2018 at 5:49 AM Matthew Singer wrote: > > I turned on syslog in busybox via its menu config and the build now fails > with the following error The correct way to turn on syslog in busybox is to ensure that "file://syslog.cfg" is included in SRC_URI. However, it looks like it's

Re: [yocto] How to update YP kernel image (run-time)

On 30/10/18 03:23, Raymond Yeung wrote: > Let's say I've a working run-time system running 2016 April release > (Krogoth) Poky image.  I've it installed previously from a USB thumb > drive onto a much bigger SSD with all partitions setup.  I don't need to > change the partition from here onward. >

Re: [yocto] Help with Nano Recipe

> It is very unusual to implement a recipe this way , and you should > rely on base classes to do that for you. For reference there is a > recipe for 'nano' in meta-oe already. > http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/nano/nano_3.0.bb?h=master And if you find

Re: [yocto] How to update YP kernel image (run-time)

On Tuesday, 30 October 2018 4:23 Raymond Yeung wrote: > Let's say I've a working run-time system running 2016 April release (Krogoth) > Poky image. > I've it installed previously from a USB thumb drive onto a much bigger SSD > with all partitions setup. > I don't need to change the partition

Re: [yocto] Help with Nano Recipe

On Tue, Oct 30, 2018 at 5:38 PM nick wrote: > > Greetings All, > I am trying to get the below recipe to build: > SUMMARY = "Recipe to build the 'nano' editor" > > PN = "nano" > PV = "2.2.6" > LICENSE="GPLv3" > > SITE = "http://www.nano-editor.org/dist; > PV_MAJOR =

Re: [linux-yocto] [PATCH][master][yocto-4.18] xfs: add xfs support

On 10/30/18 5:45 AM, Dengke Du wrote: Ceph osd daemon need to work on xfs filesystem, so add the kernel support. merged Bruce Signed-off-by: Dengke Du --- features/xfs/xfs.cfg | 5 + features/xfs/xfs.scc | 1 + 2 files changed, 6 insertions(+) create mode 100644

[yocto] Help with Nano Recipe

Greetings All, I am trying to get the below recipe to build: SUMMARY = "Recipe to build the 'nano' editor" PN = "nano" PV = "2.2.6" LICENSE="GPLv3" SITE = "http://www.nano-editor.org/dist; PV_MAJOR = "${@d.getVar('PV',d,1).split('.')[0]}" PV_MINOR = "${@d.getVar('PV',d,1).split('.')[1]}"

[yocto] Fetcher failure on mpfr 4.0.1

I'm right now seeing a fetcher failure on mpfr-4.0.1.tar.xz As far as mirrors I believe we rely on this through the inclusion of poky.conf? http://downloads.yoctoproject.org/mirror/sources/ but we also add our own (PRE)MIRRORS in the conf files. Regardless of the project, it's not enough to

[yocto] Yocto Project Status WW44’18

Current Dev Position: YP 2.6 M4 is in QA. Next Deadline: YP 2.6 M4 Release Target was Oct. 26, 2018 SWAT Team Rotation: · SWAT lead is currently: Tracy · SWAT team rotation: Tracy -> Chen on Nov. 2, 2018 · SWAT team rotation: Chen -> Armin on Nov. 9, 2018 ·

[yocto] Yocto and Debian package repositories

Hi all. I often work with Debian and I build my own repository accessible with apt. I look that when I build the image recipe many deb pacakages are produced with Packages and Release ready. How can I use this pakcages to upload all packages to a Debian customer server? Best regards,   MZ --

Re: [yocto] [selinux] sumo compilation

On 10/24/2018 7:49 PM, Joe MacDonald wrote: Hey all, I just thought I should quickly follow up on this. I have a change set ready that includes tagging and a minor tweak for sumo, integration of the current outstanding patch list and a tag for thud and a couple of additional things (possibly)

Re: [yocto] Moving to Yocto 2.3 - recipe-specific sysroots - improving the documentation

On Tue, Oct 30, 2018 at 9:05 AM CHMIELARZ Radoslaw radoslaw.chmielarz-at-leica-geosystems.com wrote: > > Hi all, > > > > I think the documentation on migrating between Yocto 2.2 and 2.3 needs > more clarification as to how did the sysroots have changed. > [...] > > > Now when trying to

[yocto] busybox build failure

I turned on syslog in busybox via its menu config and the build now fails with the following error ERROR: busybox-1.24.1-r0 do_package: QA Issue: busybox: Files/directories were installed but not shipped in any package: /lib /lib/systemd /lib/systemd/system

Re: [yocto] [meta-selinux][sumo][PATCH 1/7] layer.conf: update LAYERSERIES_COMPAT `sumo' -> `thud'

The patch set is definitely confusing. I'm not able to access git.yoctoproject.org at the moment, so I've pushed all three proposed branch updates to my fork on github. I think that's a more useful way to review these changes anyway: https://github.com/joeythesaint/meta-selinux/tree/jjm/master

Re: [yocto] "bitbake core-image-sato" yields "No package 'gdk-x11-3.0' found" build failure

On Tue, 30 Oct 2018 at 03:05, Joe Flowers wrote: > Below is the output you requested. gdk-x11-3.0.pc does not seem to exist. > > Below, should that be "wandboard" and not "qemux86" ? > > joe@ubuntu:/opt/yocto/build$ > joe@ubuntu:/opt/yocto/build$ oe-pkgdata-util find-path '*/gdk-x11-3.0.pc' >

[yocto] do_unpack: already exists and is not an empty directory

Hi, in some recipes that fetches git repository and has S variable set to "${WORKDIR}/git/foo" once per many builds we're having error: fatal: destination path 'foobar/work/x86_64-linux/squashfs-tools-native/4.2-r2/git' already exists and is not an empty directory. It happens for

[linux-yocto] [PATCH][master][yocto-4.18] xfs: add xfs support

Ceph osd daemon need to work on xfs filesystem, so add the kernel support. Signed-off-by: Dengke Du --- features/xfs/xfs.cfg | 5 + features/xfs/xfs.scc | 1 + 2 files changed, 6 insertions(+) create mode 100644 features/xfs/xfs.cfg create mode 100644 features/xfs/xfs.scc diff --git

Re: [yocto] include own script

On 10/30/2018 04:42 PM, Zolee K wrote: Hi All, Could you help me out with this? I've been experimenting with this without success, some of you have given me suggestions but neither of them worked yet. ### /recipes-z/testing$ cat testscript.bb DESCRIPTION

[yocto] include own script

Hi All, Could you help me out with this? I've been experimenting with this without success, some of you have given me suggestions but neither of them worked yet. ### /recipes-z/testing$ cat testscript.bb DESCRIPTION = "test script" LICENSE = "Zoli" SRC_URI = "file://testscript"

[yocto] Moving to Yocto 2.3 - recipe-specific sysroots - improving the documentation

Hi all, I think the documentation on migrating between Yocto 2.2 and 2.3 needs more clarification as to how did the sysroots have changed. I wanted to migrate our build system from 2.2 to 2.5 and one package in particular has caused me a day worth of scratching my head and trying different