[yocto] Powerpc64e6500 missing altivec option

Hi! When I built only poky, I had TUNE_FEATURES = "m64 fpu-hard e6500 altivec" and everything was built with -maltivec and environment-setup-ppc64e6500-poky-linux contained -m altivec: export CC="powerpc64-poky-linux-gcc -mhard-float -m64 -mcpu=e6500 -maltivec --sysroot=$SDKTARGETSYSROOT

[yocto] problem with installation pathes of recipes useing cmake + cpack

Hej I have several recipes which are based on cmake. At cmake is the "make package" enabled. It is based on CPack(debian). I am using the predefined GNU installation dirs by "include(GNUInstallDirs)" and its variables like CMAKE_INSTALL_FULL_BINDIR etc. (https://cmake.org/cmake/help/v3.0/modu

[yocto] setcap using recipe

Hello All, Is there a way to add a capability to a binary (cap_net_raw+ep),into a recipe? Example : do_install() { install -d ${D}${bindir} install -m 0755 helloworld ${D}${bindir} install -d ${D}/lib/systemd/system install -m 0755 hello.servic

Re: [yocto] setcap using recipe

Hi, On 24 June 2016 at 11:41, Kumar, Shrawan wrote: > Is there a way to add a capability to a binary (cap_net_raw+ep),into a > recipe? > > > > Example : > > do_install() { > >install -d ${D}${bindir} > >install -m 0755 helloworld ${D}${bindir} > >install -d $

Re: [yocto] setcap using recipe

Thanks Ross for your quick turn around , I am getting below error “Unable le to set CAP_SETFCAP effective capability: Operation not permitted.” But when I use# sudo setcap cap_net_raw+ep helloworldon command line I am able to set the cap. To achieve the sudo realization in recipe

Re: [yocto] setcap using recipe

What version of OE/Yocto are you using? Old versions of pseudo didn't support xattrs at all. Ross On 24 June 2016 at 13:23, Kumar, Shrawan wrote: > Thanks Ross for your quick turn around , I am getting below error > > > > “Unable le to set CAP_SETFCAP effective capability: Operation not > perm

Re: [yocto] setcap using recipe

I am using Yocto 2.0.2 Thanks and Regards Shrawan From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Friday, June 24, 2016 5:56 PM To: Kumar, Shrawan Cc: yocto@yoctoproject.org Subject: Re: [yocto] setcap using recipe What version of OE/Yocto are you using? Old versions of pseudo didn't su

[yocto] is override for UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config" necessary?

poking around UBOOT_CONFIG and UBOOT_MACHINE and, in meta-yocto-bsp, i notice the two examples of UBOOT_MACHINE being set: beaglebone.conf:UBOOT_MACHINE = "am335x_evm_config" mpc8315e-rdb.conf:UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config" while i'm sure it doesn't hurt, is there a reason

Re: [yocto] [pseudo][PATCH] Add capset pseudo function that always succeeds

I just discovered that this was never merged, Peter can you review it? Ross On 3 May 2016 at 14:18, George McCollister wrote: > The setcap utility supplied by libcap is used to set capabilities on a > file. Before setting a file's capabilities with cap_set_file() (which uses > setxattr()) it ca

Re: [yocto] setcap using recipe

Looks like using setcap directly is broken currently, there are two workarounds: 1) use a postinst to invoke setcap on the target instead 2) test the patch for pseudo that is on this list ([PATCH] Add capset pseudo function that always succeeds) and verify that it fixes the problem for you. Ross

[yocto] [meta-java] How is the version string in openjdk/openjre built

Hi, currently I'm facing a small problem with the meta-java package. I have applications that check the version string of java for specific releases. The string from java -version built with the meta-java package however does not include that but results in 1.8.0-native or 1.8.0-internal. So I wan

Re: [yocto] question: yocto-bsp tool warnings

On 2016-06-23 05:52 PM, Jake Swensen wrote: I've been looking into setting up my own BSP layer based on the standard/beaglebone branch and I've run into some warnings I wasn't familiar with. I created a test BSP with the yocto-bsp tool and set MACHINE=test, (which is the name of my meta layer) th

[yocto] [autobuilder][PATCH] nightly-arm.conf: build Cortex-A8 toolchains

Since met-fsl-arm was dropped from the nightly builds, the Cortex-A8 cross- compiler used for beaglebone builds is not created. Include toochain builds as part of nightly-arm now, so compiler is available for users of the beaglebone machine. [YOCTO #9810] Signed-off-by: Bill Randle --- buildset

[yocto] Yocto Project Status WW26

Current Dev Position: YP 2.2 M2 Next Deadline: YP 2.2 M2 cut off would be: 7/18/16 SWAT team rotation: Joshua -> Armin https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: *After delays in addressing several issues, a build of 2.2 M1 went into QA and

Re: [yocto] question: yocto-bsp tool warnings

Worked on jethro (and it's already in krogoth). Git detected a conflict that I think was only white space. >From b01d2e26bb038240fb609ef78727696c729711ba Mon Sep 17 00:00:00 2001 From: Bruce Ashfield Date: Thu, 21 Apr 2016 11:23:45 -0400 Subject: [PATCH] kernel-yocto: allow branch auditing to

[yocto] go toolchain

Hi,does someone have good go meta layer. I have experimented with meta-go and meta-golang, not able to make it work it. meta-go : bootstrap 1.4 works but the native go 1.5.3 not working. meta-golang: i am not able to make it work even with qemu x86. any suggestion appreciated. Thanks,Sridhar

Re: [yocto] go toolchain

can you try https://github.com/kraj/oe-meta-go/commits/master > On Jun 24, 2016, at 4:06 PM, Sridhar Pitchai > wrote: > > Hi, > does someone have good go meta layer. I have experimented with meta-go and > meta-golang, not able to make it wo

[yocto] [PATCH] keep platform_extra and default_platform_extra lists ordered

In RpmPM:insert_feeds_uris, the paths are kept in sets, which are unordered, but they are later used to set the priority for the Smart channels, so unexpected results could occur. Change the sets to lists and use the same code as in create_configs() to add items to the list, reather than the set op

[yocto] [meta-raspberrypi] Disable kernel option via fragment Rpi3

I'm trying to build an image for an Rpi3 and am having some difficulty. I've created and posted a meta-batman layer to bring the latest BATMAN Advanced module and userspace tools to Yocto. I haven't had any troubles getting this layer to work with other architectures, but am having troubles wi