[OE-core] Open Hardware Summit

Howdy: Just wondering if this has ever come across the official Yocto/OE radar before. The CfP includes software, which sounds like OpenEmbedded to me. Submissions are due by 25th of May 2014: http://2014.oshwa.org/participate/ Wish I would have found it sooner, but I can help write something

Re: [OE-core] OEDAM: OpenEmbedded Developers (Americas) Meeting

And a special thanks to everyone for letting the Gentoo dev crash the meeting. The meeting *was* fun and educational (especially for me). So far both the community and technology have been a lot of fun getting custom builds for various machines, as well as educational (is there an echo in here?

Re: [OE-core] Creating a machine specific recipe for config file

Package management overhead seems like a small-ish price for being able to manage/coordinate custom configs with real depends. Did I mention I like 2) better? Steve On Tue, May 27, 2014 at 11:35 AM, Saul Wold s...@linux.intel.com wrote: Folks, We have had an open enhancement in the form

Re: [OE-core] Creating a machine specific recipe for config file

Actually, that's not bad either. As long as the magic is documented, that sounds pretty good too. Steve On Tue, May 27, 2014 at 1:44 PM, Christopher Larson clar...@kergoth.comwrote: On Tue, May 27, 2014 at 1:39 PM, Darren Hart dvh...@linux.intel.comwrote: On 5/27/14, 11:35, Saul Wold

[OE-core] libgcrypt workaround

OE-devs/Tim: Here's the basic recipe patch; not sure if I should submit it formally or not. Maybe a configure patch is preferred? Feedback welcome. Thanks, Steve diff --git a/meta/recipes-support/libgcrypt/libgcrypt.inc b/meta/recipes-support/libgcrypt/libgcrypt.inc index bba4a79..bd4eedd

Re: [OE-core] libgcrypt workaround

, That workaround fixes the problem, but I think there is something fundamentally wrong deeper in. Looks like the culprit is pkgconfig.patch for libgpg-error. Testing and will send patch. On Wed, Jul 16, 2014 at 6:47 PM, Stephen Arnold stephen.arnol...@gmail.com wrote: OE-devs/Tim: Here's

Re: [OE-core] How to force patch application

Not sure if there's an easy way with quilt (check the quilt options) but a relatively easy way would be to use your own patch routine (essentially anything you want). One thing you could do is disable the normal patch application (add ;patch=0 to the end of the patch line in SRC_URI) and then use

Re: [OE-core] How to force patch application

--force option) at my own risk. Do you see any solution? Giuseppe 2014-08-07 16:43 GMT+02:00 Stephen Arnold stephen.arnol...@gmail.com: Not sure if there's an easy way with quilt (check the quilt options) but a relatively easy way would be to use your own patch routine (essentially anything

Re: [OE-core] on current linux distros, what are potential candidates for ASSUME_PROVIDED?

I would agree that for classroom purposes, some of the best time savers are things like pre-fetching downloads to a local machine, pre-cloning kernel repos, and shared cache. Also, IIRC several of the course lab examples (in the LF Yocto course) didn't quite work as expected (mostly kernel

Re: [OE-core] [oe] Fwd: open source conference in Honduras needs Yocto Project/Openembedded/OpenHardware speaker

the proposal I will only need to re-check my schedule to validate availability. Please let me know if this works. thanks for your time, On Thu, Jun 4, 2015 at 10:27 AM, Stephen Arnold stephen.arnol...@gmail.com wrote: That works if you have some travel coverage, unfortunately I just heard Diego

[OE-core] open source conference in Honduras needs Yocto Project/Openembedded/OpenHardware speaker

There seems to be plenty of room (only 2 or 3 speakers signed up so far) and they'd love to have an official LF (or just embedded linux) speaker. I've been invited to speak, and they can cover the normal fees/lodging/food for speakers (just not the travel costs, so I'm still working things out

Re: [OE-core] [oe] Fwd: open source conference in Honduras needs Yocto Project/Openembedded/OpenHardware speaker

: Stephen Arnold stephen.arnol...@gmail.com To: Patches and discussions about the oe-core layer openembedded-core@lists.openembedded.org There seems to be plenty of room (only 2 or 3 speakers signed up so far) and they'd love to have an official LF (or just embedded linux) speaker. I've been

Re: [OE-core] [oe] Fwd: open source conference in Honduras needs Yocto Project/Openembedded/OpenHardware speaker

schedule to validate availability. Please let me know if this works. thanks for your time, On Thu, Jun 4, 2015 at 10:27 AM, Stephen Arnold stephen.arnol...@gmail.com wrote: That works if you have some travel coverage, unfortunately I just heard Diego is in the hospital (no details yet

[OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

The main thing is build failures with gold linker, but qemu is also a little too aggressive at finding random tools on the build host, so we also set the build env for qemu-native and make sure it doesn't reset its own (hard-coded) cflags when we don't want it to. Signed-off-by: Stephen Arnold

[OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

The main thing is build failures with gold linker, but qemu is also a little too aggressive at finding random tools on the build host, so we also set the build env for qemu-native and make sure it doesn't reset its own (hard-coded) cflags when we don't want it to. Signed-off-by: Stephen Arnold

Re: [OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

Okay, that wasn't supposed to cut off the v2 after PATCH... Anyway, this is/was v2 for master branch (needs testing). Steve On Sun, Jun 12, 2016 at 6:09 PM, Stephen Arnold <sarn...@vctlabs.com> wrote: > The main thing is build failures with gold linker, but qemu is also a >

Re: [OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

Following this: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and it still strips my " v3" from PATCH. Is there another document/prefix format I should be looking at? Thanks, Steve On Sun, Jun 19, 2016 at 12:40 PM, Stephen Arnold <sarn...@vctla

[OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

The main thing is build failures with gold linker, but qemu is also a little too aggressive at finding random tools on the build host, so we also set the build env for qemu-native and make sure it doesn't reset its own (hard-coded) cflags when we don't want it to. Signed-off-by: Stephen Arnold

Re: [OE-core] [PATCH v4] qemu-native: set ld.bfd, fix cflags, and set some environment vars

And I finally figured out git send-email no longer has a --subject-prefix= option so it looks like --compose and hand-edit the Subject line in the patch is the only way to increment the version. This is [PATCH v4] btw... Steve On Mon, Jun 20, 2016 at 5:54 PM, Stephen Arnold <sarn...@vctlabs.

Re: [OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

185 didn't need to be rerun and 1 failed. Summary: 1 task failed: virtual:native:/home/sarnold/beagleboard-bsp/poky/meta/recipes-devtools/qemu/qemu_2.5.0.bb, do_compile On Wed, Jun 15, 2016 at 2:03 PM, Khem Raj <raj.k...@gmail.com> wrote: > On Sun, Jun 12, 2016 at 6:09 PM, Stephen Arn

Re: [OE-core] [PATCH v4] qemu-native: set ld.bfd, fix cflags, and set some environment vars

t; -Original Message- >> From: openembedded-core-boun...@lists.openembedded.org >> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf >> Of Robert Yang >> Sent: Thursday, June 23, 2016 3:55 PM >> To: Stephen Arnold <stephen.arnol...@gmail.com

Re: [OE-core] Problems with perl 5.22

As another point of information, I'm having similar issue with perl 5.22.1 on some arm boxes (native Gentoo builds) and even some odd build differences between amd box and intel corei5 9 (I know, weird...). The issue I'm hitting is basically a horribly broken upstream Configure script, and in my

Re: [OE-core] Aarch64 u-boot with gcc .5x

I hit the same thing and ended up using their prebuilt bootloader to get it up for testing. There is a big C++ ABI change with gcc 5.x (I've been using 5.3.0 for a while now) and the gold linker is much less tolerant of underlinking than bfd is. That said, their u-boot is funky but not actually

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

Thanks, our timing is great (since I just did the same thing on Saturday but didn't send anything to the list yet). Still have some testing to do to see if it actually works; recipes are here: https://github.com/sarnold/meta-small-arm-extra/commits/master On Mon, Aug 1, 2016 at 4:01 AM, Fan Xin

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

<ross.bur...@intel.com> wrote: > Hi, > > On 1 August 2016 at 18:13, Stephen Arnold <stephen.arnol...@gmail.com> > wrote: >> >> Thanks, our timing is great (since I just did the same thing on >> Saturday but didn't send anything to the list yet). Still have some &g

Re: [OE-core] [PATCH] Replace foomatic-filters with cups-filters

No answer to this? cups-filters would be kinda important for actual printing, especially since the existing ghostscript/cups/poppler packages have all been gutted of anything called *toraster. The current state (on krogoth at least) is completely broken; is there something on another branch

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

sorry, you missed a couple of replies I guess... It's in the Ross repo now: https://github.com/rossburton/meta-printing Steve On Tue, Aug 2, 2016 at 5:59 PM, Fan Xin <fan@jp.fujitsu.com> wrote: > > On 2016年08月03日 02:33, Stephen Arnold wrote: >> >> Hey, don't keep

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

and we can take a look at merging. Steve On Mon, Aug 1, 2016 at 11:48 PM, Fan Xin <fan@jp.fujitsu.com> wrote: > > > On 2016年08月02日 02:24, Burton, Ross wrote: >> >> >> On 1 August 2016 at 18:22, Stephen Arnold <stephen.arnol...@gmail.com >>

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

t 02:42, Fan Xin <fan@jp.fujitsu.com> wrote: >> >> >> >> On 2016年08月03日 10:12, Stephen Arnold wrote: >>> >>> sorry, you missed a couple of replies I guess... >>> >>> It's in the Ross repo now: >>> >>> https://github.com/ro

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

Trying to remember what my dad said about "Ask a silly question..." Steve On Mon, Aug 1, 2016 at 10:24 AM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 1 August 2016 at 18:22, Stephen Arnold <stephen.arnol...@gmail.com> > wrote: >> >> That's actua

Re: [OE-core] [PATCH v2] Replace foomatic-filters with cups-filters

On Tue, Aug 2, 2016 at 12:23 PM, Burton, Ross wrote: [snip] > In a desperate attempt to keep the ball rolling I propose this repo as a > starting point: > > https://github.com/rossburton/meta-printing > > It's basically a new layer containing foomatic, ghostscript and cups

[OE-core] [PATCH] qemu-native: set ld.bfd, fix cflags, and set some environment vars

The main thing is build failures with gold linker, but qemu is also a little too aggressive at finding random tools on the build host, so we also set the build env for qemu-native and make sure it doesn't reset its own (hard-coded) cflags when we don't want it to. Signed-off-by: Stephen Arnold

[OE-core] [PATCH] RfC: Incomplete morty toolchain config (gcc-6.2 in poky and oe-core)

Above toolchain breaks in both possible sets of metadata on hardened host (hardened amd64 profile with PAX kernel). This issue does not occur on krogoth or older branches with 5.4 or previous gcc versions. Rolling back to 5.4 toolchain in morty results in random build failures from the kernel

[OE-core] [meta-oe][PATCH] Add fix for missing no-PIE flags in gcc-6.2

From: Stephen Arnold <stephen.arnol...@gmail.com> Fixes build on hardened PAX host with gcc-5 (linker error on relocs). Completes no-PIE config by adding to ALL_* flags variables. Borrowed from Gentoo gcc patches, tested on 2 hardened amd64 hosts. Upstream-Status: Inappropriate [configu

[OE-core] [meta-oe][PATCH v2] gcc-6.2: Add fix for missing no-PIE flags

From: Stephen Arnold <stephen.arnol...@gmail.com> Fixes build on hardened PAX host with gcc-5 (linker error on relocs). Completes no-PIE config by adding to ALL_* flags variables. Borrowed from Gentoo gcc patches, tested on 2 hardened amd64 hosts. Upstream-Status: Inappropriate [configu

[OE-core] gcc-6: Add fix for missing no-PIE flags

From: Stephen Arnold <stephen.arnol...@gmail.com> Fixes build on hardened PAX host with gcc-5 (linker error on relocs). Completes no-PIE config by adding to ALL_* flags variables. Borrowed from Gentoo gcc patches, tested on 2 hardened amd64 hosts. Upstream-Status: Inappropriate [configu

[OE-core] [krogoth][meta-python]][PATCH] python-evdev: add setup.py patch to make sure it uses sysroot headers

From: Steve Arnold This currently works (randomly) when BUILD_HOST headers are a close enough match, but fails as soon as they differ, due to static header include paths in setup.py. This patch adds a path check for the STAGING_INC dir and makes it use the right

[OE-core] [krogoth][meta-python]][PATCH v2] python-evdev: add setup.py patch

From: Steve Arnold This currently works (randomly) when BUILD_HOST headers are a close enough match, but fails as soon as they differ, due to static header include paths in setup.py. This patch adds a path check for the STAGING_INC dir and makes it use the right

Re: [OE-core] Crazy display

I do mostly remote screen sessions (on gentoo host, sometimes ubuntu/debian vm) and occasional local terminal (xfce term but remote could be console only). The fact that I have not seen this once is just *weird* (and I'm pretty damn good about hitting the annoying bits). Steve On Mon, Oct 3,