[yocto] Yocto Project Status WW25'19

Current Dev Position: YP 2.8 M2 Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019 SWAT Team Rotation: * SWAT lead is currently: Paul * SWAT team rotation: Paul -> Ross on June 21, 2019 * SWAT team rotation: Ross -> Amanda on June 28, 2019 *

Re: [yocto] cortexa9t2hf instead of cortexa9hf

> bitbake is still just a parser of the metadata and executor of our > tasks, it doesn't (and shouldn't) need to know anything about arm silicons. You precisely formulated my latest thoughts in one sentence. :-) Cheers, Zoran ___ On Tue, Jun 18, 2019 at 9:03 PM Martin Jansa wrote: > > On Tu

Re: [yocto] cortexa9t2hf instead of cortexa9hf

On Tue, Jun 18, 2019 at 08:47:32PM +0200, Zoran Stojsavljevic wrote: > > Just ARM_INSTRUCTION_SET to "arm" which will give you "cortexa9hf" again > > (not "armv7a"). > > I think this is impossible for the current state of YOCTO affairs. I > do not think bitbake is able to determine type of arm sil

Re: [yocto] cortexa9t2hf instead of cortexa9hf

> Just ARM_INSTRUCTION_SET to "arm" which will give you "cortexa9hf" again > (not "armv7a"). I think this is impossible for the current state of YOCTO affairs. I do not think bitbake is able to determine type of arm silicon, since it needs to implement the following instruction somewhere beneath (

Re: [yocto] cortexa9t2hf instead of cortexa9hf

On Mon, Jun 17, 2019 at 07:47:36PM +0200, Arno Steffens wrote: > Thanks for explaining this. > I take some time to read about thumb/thumb2. The feedback is mixed. It seems > to generate more compact code, but some say it speeds up, others it slows > down because of reduced function set - and it c

Re: [yocto] devshell env in warrior

Hey Khem, Check that Makefiles are not overriding CC/CXX/LD etc. some old crufty > Makefiles I have seen doing that, you might see something like In the recipe it's caused by 'inherit module', which is needed because part of the recipe is building modules. I would understand this would unset CFLA

Re: [yocto] cortexa9t2hf instead of cortexa9hf

On Mon, Jun 17, 2019 at 10:48 AM Arno Steffens wrote: > > Thanks for explaining this. > I take some time to read about thumb/thumb2. The feedback is mixed. It seems > to generate more compact code, but some say it speeds up, others it slows > down because of reduced function set - and it can cau

Re: [yocto] devshell env in warrior

On Mon, Jun 17, 2019 at 4:55 PM matthew stanger wrote: > > I'm trying to figure out why when running devshell in Warrior CC/CFLAGS are > not the same as do_compile for a recipe. For example. > devshell printenv yields: > CC=aarch64-poky-linux-gcc -fuse-ld=bfd > -fmacro-prefix-map=/home/matt/rd

Re: [yocto] [PATCH 3/3] recipes-bsp/u-boot: update to the latest version

On 09/05/2019 01:30, Trevor Woerner wrote: a previous patch of yours did a:     require recipes-bsp/u-boot/u-boot-common.inc which defines this SRCREV my subtle point being: I don't get the impression you're testing your patches, or at least not testing them correctly. I did the test before

Re: [yocto] [meta-mono][PATCH] mono-5.xx: fix an issue with too long paths in doltlibtool

Ping #2! Alex On Mon, 27 May 2019 at 12:22, Alex J Lennon wrote: > > Thanks for the reminder Alex > On 27/05/2019 11:16, Alexander Kanavin wrote: > > Ping? > > Alex > > On Mon, 13 May 2019 at 18:25, Alexander Kanavin > wrote: > > When build directory is deeply nested, the shebang limit of 12