[yocto] [meta-virtualization][PATCH] libvirt: remove qemu from PACKAGECONFIG for mips n32 and n64

From: Kai Kang PACKAGECONFIG 'qemu' causes libvirt depends on package qemu. But qemu is not compatible with mips n32 and n64. So remove 'qemu' from PACKAGECONFIG for mips n32 and n64. Signed-off-by: Kai Kang Signed-off-by: Mark Hatle --- recipes-extended/libvirt/libvirt_4.7.0.bb | 4 1 f

Re: [yocto] [OE-core] YP 2.7 Planning

No, that will be suggested and hopefully agreed on in the 11/6 Technical meeting, as well as the exact milestone dates. Stephen From: akuster808 [mailto:akuster...@gmail.com] Sent: Monday, October 15, 2018 8:22 AM To: Jolley, Stephen K ; yocto@yoctoproject.org; openembedded-c...@lists.openembed

Re: [yocto] [Yocto][poky][meta] already-stripped ignore if set for any other package then INSANE_SKIP_${PN}

Ah yes, of course. Stripping happens *before* package splitting, so it doesn't make sense to have it set on PN-package1. Just set it on PN and it should work. Ross On Mon, 15 Oct 2018 at 08:18, Måns Zigher wrote: > > Hi, > > Sorry I see now that there is a typo. What I mean is that in the defau

Re: [yocto] permissions when installing scripts

cp --preserve=mode might prevent that. However, I'm wondering why the +x gets lost in the first place. Normal GNU copy seems to copy that flag by default. Even when doing it as root using sudo. Aren't we looking in the wrong place for the executable bit(s) to fall off? -- Bas. On 2018-1

Re: [yocto] permissions when installing scripts

Hi Bas, On Mon, Oct 15, 2018 at 8:45 PM Bas Mevissen wrote: > > > > cp -a or --preserve(=) optionally combined with other options > does the trick. However, using install is the better solution. But -p will keep current user and not root used when installed in final rootfs (also QA report warning

Re: [yocto] permissions when installing scripts

cp -a will preserve ownership, which you don't want. Ross On Mon, 15 Oct 2018 at 19:45, Bas Mevissen wrote: > > > > cp -a or --preserve(=) optionally combined with other options > does the trick. However, using install is the better solution. > > > -- Bas. > > On 2018-10-15 14:35, Burton, Ross wr

Re: [yocto] permissions when installing scripts

cp -a or --preserve(=) optionally combined with other options does the trick. However, using install is the better solution. -- Bas. On 2018-10-15 14:35, Burton, Ross wrote: As you've discovered, cp doesn't preserve permissions. Using install -m755 is the idiom. Ross On Mon, 15 Oct 2018

Re: [yocto] Add python2 as native package in openembedded sdk

Add nativesdk-python-core and nativesdk-python-modules to TOOLCHAIN_HOST_TASK (using _append). Ross On Mon, 15 Oct 2018 at 17:30, Alberto Eusebi wrote: > > Hello, > I need to cross compile python2 packages using openembedded sdk. The sdk > resulting package contains only python 3.5.3 (in older ve

[yocto] populate_sdk fails when multilib enabled

Hi Guys, I am having customized Apollo Lake Board. Using generic meta-intel layer with MACHINE=intel-corei7-64, Branch = sumo We wanted to support 32-bit libraries, so added multilib in local.conf require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x8

[yocto] Add python2 as native package in openembedded sdk

Hello, I need to cross compile python2 packages using openembedded sdk. The sdk resulting package contains only python 3.5.3 (in older version it contains python 2.7.3 as well). _ # ls -l sysroots/x86_64-angstromsd

Re: [yocto] [OE-core] YP 2.7 Planning

Stephen, On 10/15/2018 08:05 AM, Jolley, Stephen K wrote: > > All, > >   > > We have begun planning for YP 2.7.   In prior versions, items that we > didn’t have the bandwidth to do were assigned the target milestone of > 2.99.  Since YP 2.7 planning has just begun, I would like each of you > to r

[yocto] YP 2.7 Planning

All, We have begun planning for YP 2.7. In prior versions, items that we didn't have the bandwidth to do were assigned the target milestone of 2.99. Since YP 2.7 planning has just begun, I would like each of you to review the bugs and enhancements in YP 2.99 and determine if you will have th

[yocto] Yocto Project Unassigned Bugs - Help Needed

All, The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the tr

[yocto] yocto raspberrypi showing default splash instead of raspberrypi splash

I tried to build rpi-basic-image and core-image-base ( rpi-basic-image.bb suggest to build core-image-base because rpi-basic-image is deprecated) for raspberry pi zero wifi. I am able to build and boot these images. But these images shows yocto splash instead of raspberry pi splash. Please find at

Re: [yocto] permissions when installing scripts

As you've discovered, cp doesn't preserve permissions. Using install -m755 is the idiom. Ross On Mon, 15 Oct 2018 at 11:12, Belisko Marek wrote: > > Hi, > > I have package which contains bunch of scripts (with +x flag for > user). When installed in do_install method (simply by copying them to >

[yocto] permissions when installing scripts

Hi, I have package which contains bunch of scripts (with +x flag for user). When installed in do_install method (simply by copying them to destination) they loose +x flag. I know copying directly is not best approach but there exists better way how to keep scripts permissions like in repo (except

Re: [yocto] [Yocto][poky][meta] already-stripped ignore if set for any other package then INSANE_SKIP_${PN}

Hi, Sorry I see now that there is a typo. What I mean is that in the default package I am not suing INSANE_SKIP but for packag1 I need already-stripped INSANE_SKIP_${PN}-package1 = " \ dev-so \ already-stripped \ " But I continuously get the error that they are already-stripped. So is it suppose