[oe] [meta-filesystems][PATCH] zfs: update to 2.2.2

From: Bruce Ashfield In addition to the zfs upstream commits: - This fixes the build against libc-headers/kernel 6.6+ - adds bash-completion packaging, as 2.2.2 has support Bumping zfs to version zfs-2.2.2, which comprises the following commits: 494aaaed8 Tag zfs-2.2.2 522414da3

Re: [oe] openssl-native.rm_work runs before kernel-module.install -> no signature

On Fri, Nov 3, 2023 at 3:49 AM Jörg Sommer wrote: > > On 30.10.23 14:24, Jörg Sommer via lists.openembedded.org wrote: > > On 30.10.23 13:29, Bruce Ashfield wrote: > >> On Mon, Oct 30, 2023 at 4:40 AM Jörg Sommer > >> wrote: > >>> On 26.10.23 17:

Re: [oe] openssl-native.rm_work runs before kernel-module.install -> no signature

On Mon, Oct 30, 2023 at 4:40 AM Jörg Sommer wrote: > > On 26.10.23 17:25, Bruce Ashfield wrote: > > On Thu, Oct 26, 2023 at 7:16 AM Jörg Sommer > > wrote: > >> > >> On 26.10.23 10:34, Jose Quaresma wrote: > >>> > >>> > >>>

Re: [oe] openssl-native.rm_work runs before kernel-module.install -> no signature

On Thu, Oct 26, 2023 at 7:16 AM Jörg Sommer wrote: > > On 26.10.23 10:34, Jose Quaresma wrote: > > > > > > Khem Raj mailto:raj.k...@gmail.com>> escreveu no > > dia quarta, 25/10/2023 à(s) 18:18: > > > > I wonder if something like below would help > > > > diff --git > >

Re: [oe] openssl-native.rm_work runs before kernel-module.install -> no signature

On Wed, Oct 25, 2023 at 7:40 AM Jose Quaresma wrote: > > Hi Joerg, > > This topic has already been discussed previously in > https://lists.openembedded.org/g/openembedded-core/topic/98296212 > > Bruce even sent a patch but it was never integrated, probably because it was > a very invasive

[oe] [PATCH 2/2 v2][meta-oe] vboxguestdrivers: fix kernel v6.5 build

From: Bruce Ashfield When building against the 6.5 kernel (and kernel headers), the following build error is encountered: | vboxguestdrivers/7.0.10/vboxguestdrivers-7.0.10/vboxvideo/vbox_fb.c:194:24: error: 'drm_fb_helper_sys_fillrect' undeclared here (not in a function); did you mean

[oe] [PATCH 1/2 v2][meta-oe][meta-filsystems] zfs: update to v2.2.0-rc4

From: Bruce Ashfield Building against the 6.5+ kernel and headers resulted in a build failure due to missing detected features. We can fix the issues by bumping to 2.2.0-rc4 Bumping zfs to version zfs-2.2.0-rc4-35-g229ca7d73, which comprises the following commits: 739db06ce Tag 2.2.0-rc4

Re: [oe] /home/bruce/rr.meta-oe/0002-vboxguestdrivers-fix-kernel-v6.5-build.patchFrom 2981fa9167f70444f657c53d80f23496b209b5bd Mon Sep 17 00:00:00 2001

m default to 'off' everywhere > f917cf1c0 Fix the ZFS checksum error histograms with larger record > sizes > 56ed389a5 Fix raw receive with different indirect block size. > e613e4bbe Avoid extra snprintf() in dsl_deadlist_merge(). > b4e630b00 Add missed DMU_PR

[oe] /home/bruce/rr.meta-oe/0002-vboxguestdrivers-fix-kernel-v6.5-build.patchFrom 2981fa9167f70444f657c53d80f23496b209b5bd Mon Sep 17 00:00:00 2001

JECT prefetch. bf6cd3079 FreeBSD: catch up to __FreeBSD_version 1400093 1266cebf8 FreeBSD: Fix build on stable/13 after 1302506. Signed-off-by: Bruce Ashfield --- Khem, With 6.4 going EOL upstream, I'm rushing in a bump to v6.5 for OEcore. This is a bump for btfs that solves issues

[oe] [PATCH 2/2] vboxguestdrivers: fix kernel v6.5 build

From: Bruce Ashfield When building against the 6.5 kernel (and kernel headers), the following build error is encountered: | vboxguestdrivers/7.0.10/vboxguestdrivers-7.0.10/vboxvideo/vbox_fb.c:194:24: error: 'drm_fb_helper_sys_fillrect' undeclared here (not in a function); did you mean

[oe] [meta-oe][PATCH] vboxguestdrivers: fix compilation against 6.4 kernel / headers

From: Bruce Ashfield The vboxguest drivers (vboxsf) fail to build against the 6.4 kernel due to iovec iterator changes. This is a port of the gentoo patches (which are picked from the upstream virtualbox repository) to address the compilation issues. We obviously can drop these when the next

[oe] [PATCH][meta-filesystems] zfs: update to 2.1.7

From: Bruce Ashfield Bumping zfs to fix builds for 6.x+ kernel versions (and libc-headers), and we also pickup the following commits: 21bd76613 Tag zfs-2.1.7 7819b12f2 zfs-2.1.7: Use ubuntu-20.04 for zloop and sanity builders c8d2ab05e Fix setting the large_block feature after

[oe] [PATCH] vboxguestdrivers: make kernel shared directory dependency explicit

From: Bruce Ashfield When fixing the build against 5.19, we added a copy of stdarg.h out of the kernel source. That of course works fine if the kernel-source has already been staged, but is an error otherwise. We add the explicit dependency to the export_source task, to make sure

[oe] [PATCH][meta-filesystems] zfs: update to v2.1.5

From: Bruce Ashfield Updating to 2.1.5 primarily for kernel 5.19+ support. We refresh one patch, and pick up the following changes: Changes - Remove install of zfs-load-module.service for dracut #13574 - FreeBSD: Silence clang unused-but-set-variable - Improve sorted scan memory

[oe] [PATCH][meta-oe] vboxguestdrivers: fix build against 5.19 kernel / libc-headers

From: Bruce Ashfield We've bounced back and forth with the mixed libc/kernel module structure of these drivers. In particular the location and content of stdarg.h has caused compile problems, or can't be located. In particular kernel versions have issues with stdarg.h and compatibility

Re: [oe] [yocto] How to force build system to use a working kernel defconfig?

On Thu, Apr 28, 2022 at 5:39 AM Jupiter wrote: > > Hi Bruce, > > Thanks for your response. > > > You can't suppress the kernel's config step, it is always going to > > run. You can't just copy over .config and have the kernel build. > > If the OE build kernel config step can be disabled to

Re: [oe] Honister customer defconfig replacement doesn't work

On Wed, Apr 27, 2022 at 6:09 PM JH wrote: > > Hello, > > My apology, I am not sure which group is working on defconfig syntax > for version 3.4 Honister branch. I posted the question to Yocto list > without response, let me rephrase it again: oe-core/yocto are the right place to ask. I can

[PATCH][oe][meta-python] python: remove recipes imported to oe-core

From: Bruce Ashfield To support device tree schema validation in kernels v5.16+, we've imported dt-schema + dependencies to core. So we can safely drop them from meta-python. Signed-off-by: Bruce Ashfield --- ...e-pytest-runner-to-test_requirements.patch | 32 - .../python/python3

Re: [oe] [meta-networking][PATCH] mctp: Fix build with 5.15+ kernel headers

On Fri, Nov 5, 2021 at 4:24 PM Khem Raj wrote: > > Signed-off-by: Khem Raj > Cc: Bruce Ashfield Looks good to me, and it fixed the build for me as well. Bruce > --- > .../0001-build-Adjust-for-kernel-mctp.h.patch | 84 +++ > .../recipes-support/mctp/mctp_gi

Re: [oe] [meta-oe][PATCH] sdbus-c++-libsystemd: Fix build with kernel 5.15+

; Signed-off-by: Khem Raj > Cc: Bruce Ashfield > --- > ...-linux-Sync-if_arp.h-with-Linux-5.14.patch | 29 +++ > .../sdbus-c++/sdbus-c++-libsystemd_243.bb | 1 + > 2 files changed, 30 insertions(+) > create mode 100644 > meta-oe/recipes-core/sdbus-c++/sd

[oe] [PATCH][meta-oe] vboxguestdrivers: fix build against 5.15 kernel/libc-headers headers

From: Bruce Ashfield In kernel v5.15+ stdarg.h is part of the kernel source, and the upstream project has a change to prefer that stdarg.h to the c-library variant and hence includes it as , which leads to the following build error: | In file included from ../vboxsf/include/iprt/types.h:34

Re: [oe] [meta-oe][PATCH] vboxguestdrivers: upgrade 6.1.26 -> 6.1.28

oxguestdrivers/vboxguestdrivers/r90497-regops-5.14-fix.patch >> >> > rename >> >> > meta-oe/recipes-support/vboxguestdrivers/{vboxguestdrivers_6.1.26.bb => >> >> > vboxguestdrivers_6.1.28.bb} (92%) &g

Re: [oe] [meta-oe][PATCH] vboxguestdrivers: upgrade 6.1.26 -> 6.1.28

; >> > > >> > b/meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers/r89690-5.14-fixes.patch > >> > deleted file mode 100644 > >> > index 951bd5013..0 > >> > --- > >> > a/meta-oe/recipes-support/vboxguestdrivers/vbox

[oe] [meta-oe][PATCH] vboxguestdrivers: fix build against 5.14+

From: Bruce Ashfield The bump of the reference / default kernels and libc-headers to 5.14 in oe-core broke the build of the vbox guest drivers. The upstream SVN already has 5.14 fixes for the issues, so these are SVN exports of the changes. When a new release is available, we can drop

Re: [oe] [meta-oe][PATCH] vboxguestdrivers: Fix build with kernel 5.10

9:22 AM Khem Raj wrote: > > > > > > > > On 1/5/21 9:12 AM, Bruce Ashfield wrote: > > > On Tue, Jan 5, 2021 at 12:05 PM Khem Raj wrote: > > >> > > >> > > >> > > >> On 1/5/21 2:50 AM, Jose Quaresma wrote: > >

Re: [oe] [meta-oe][PATCH] vboxguestdrivers: Fix build with kernel 5.10

On Tue, Jan 5, 2021 at 12:05 PM Khem Raj wrote: > > > > On 1/5/21 2:50 AM, Jose Quaresma wrote: > > Hi, > > > > I think there are a typo in python version the patch mention 5.9 instead > > of 3.9 > > thanks I will fix it Ha! Sorry about the double send of the fix, I checked the list this

[oe] [PATCH] vboxguestdrivers: fix build against kernel v5.10+

From: Bruce Ashfield We need to adjust the vboxguest drivers to build against kernels 5.10+. These are backports from the virtual box SVN repository and can be dropped in future uprevs. Signed-off-by: Bruce Ashfield --- ...-linux-drm-Adjustment-for-Linux-5.10.patch | 321

Re: [oe] [PATCH] menuconfig,mconf-cfg: Allow specification of ncurses location

On Tue, Dec 1, 2020 at 7:42 PM Scott Branden wrote: > Hi Bruce, > > On 2020-12-01 11:01 a.m., Bruce Ashfield wrote: > > On Tue, Dec 1, 2020 at 12:19 PM Scott Branden > > wrote: > >> Hi Masahiro, > >> > >> On 2020-12-01 4:25 a.m., Masahiro Yam

Re: [oe] [PATCH] menuconfig,mconf-cfg: Allow specification of ncurses location

On Tue, Dec 1, 2020 at 12:19 PM Scott Branden wrote: > > Hi Masahiro, > > On 2020-12-01 4:25 a.m., Masahiro Yamada wrote: > > On Sat, Nov 28, 2020 at 9:45 AM Scott Branden > > wrote: > >> From: Bruce Ashfield > >> > >> In some cross

Re: [oe] all external kernel modules fail to compile with with poky and linux 5.10-rc1

On Thu, Nov 12, 2020 at 9:21 PM Anuj Mittal wrote: > > On Thu, 2020-11-12 at 15:57 -0800, Scott Branden via > lists.openembedded.org wrote: > > It appears the all external modules fail to compile if you try using > > the 5.10-rc1 or later kernel due to this commit: > >

Re: [oe] all external kernel modules fail to compile with with poky and linux 5.10-rc1

On Thu, Nov 12, 2020 at 6:57 PM Scott Branden via lists.openembedded.org wrote: > > It appears the all external modules fail to compile if you try using the > 5.10-rc1 or later kernel due to this commit: >

Re: [oe] Tracking dependencies on kernel configration

On Sat, Oct 3, 2020 at 1:49 AM Khem Raj wrote: > > On Fri, Oct 2, 2020 at 7:27 PM Bruce Ashfield > wrote: > > > > On Fri, Oct 2, 2020 at 4:21 PM Khem Raj wrote: > > > > > > On Fri, Oct 2, 2020 at 11:28 AM Bruce Ashfield > > > wrote: > > &

Re: [oe] Tracking dependencies on kernel configration

On Fri, Oct 2, 2020 at 1:58 PM Maxim Sloyko via lists.openembedded.org wrote: > > Hi all, > > I hope this is the right mailing list for my question. > > Short version: my recipe (not kernel) depends on a certain option(s) > being set in the kernel built and certain devices enabled in the > device

Re: [oe] Kernel 5.3 fails to compile No rules to make zImage

On Thu, Oct 3, 2019 at 8:07 AM JH wrote: > > Hi Bruce, > > On 10/1/19, Bruce Ashfield wrote: > > On Tue, Oct 1, 2019 at 7:22 AM JH wrote: > >> > >> Hi, > >> > >> I am building kernel 5.3 on imx6 but failed in do_compile, is anyone

Re: [oe] Kernel 5.3 fails to compile No rules to make zImage

On Tue, Oct 1, 2019 at 7:22 AM JH wrote: > > Hi, > > I am building kernel 5.3 on imx6 but failed in do_compile, is anyone > able to compile kernel 5.3? I don't build for the im6, but linux-yocto-dev has been building and booting for v5.3 throughout the entire -rc and release cycle for that

Re: [oe] [meta-realtime][PATCH] layer.conf: add openembedded-layer to LAYERDEPENDS

Indeed. If khem hadn't followed up, I wouldn't have seen this at all. I have grabbed the patch and merged it, but in the future, the linux-yocto list is the one we are (re)using for the realtime stuff. Bruce On Tue, Sep 3, 2019 at 11:31 AM Khem Raj wrote: > > please send this to

[oe] [meta-networking][PATCH] dnsmasq: fix build against 5.2 headers

From: Bruce Ashfield Upstream linux y2038 work has moved some definitions SIOCGSTAMP is defined in linux/sockios.h, not asm/sockios.h now. So we need to add that include to fix the build. Upstream-status: backport of http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h

Re: [oe] [meta-networking][RFC PATCH 0/1] Failed to compile networkmanager with musl

On Wed, Aug 28, 2019 at 12:27 AM Khem Raj wrote: > > On Tue, Aug 27, 2019 at 8:43 PM wrote: > > > > From: Kai Kang > > > > Hi Khem, > > > > I am updating networkmanager to 1.20. But I meet a problem with musl > > that "error: redefinition of 'struct ethhdr'". I find a patch for kernel > > which

Re: [oe] [meta-oe][PATCH] libseccomp: import from meta-security

On Thu, Jul 25, 2019 at 11:01 PM Yu, Mingli wrote: > > > > On 2019年07月26日 10:46, Bruce Ashfield wrote: > > > > > > On Thu, Jul 25, 2019 at 10:28 PM Yu, Mingli > <mailto:mingli...@windriver.com>> wrote: > > > > > > > > On

Re: [oe] [meta-oe][PATCH] libseccomp: import from meta-security

On Thu, Jul 25, 2019 at 10:28 PM Yu, Mingli wrote: > > > On 2019年07月25日 21:45, Bruce Ashfield wrote: > > On Thu, Jul 25, 2019 at 3:06 AM wrote: > >> > >> From: Mingli Yu > > > > Can you share some details as to why this should be pulled

Re: [oe] [meta-oe][PATCH] libseccomp: import from meta-security

On Thu, Jul 25, 2019 at 3:06 AM wrote: > > From: Mingli Yu Can you share some details as to why this should be pulled from meta-security into a different repo ? It seems to fit the mandate of meta-security quite nicely ;) Is there some sort of dependency issue, or other technical problem that

Re: [oe] [meta-filesystems][PATCH] ostree: import from meta-overc

On Thu, Jul 25, 2019 at 3:05 AM wrote: > > From: Mingli Yu This doesn't make any sense to "import from meta-overc". meta-overc, was never the authoritative upstream for ostree. That layer has to carry a specific version to meet the requirements of some of the container libraries, etc, that it

Re: [oe] [meta-virtualization] [meta-virt][m-c-s][v2][PATCH 1/1] libibverbs: do not try to build for arm 32 bit or any mips

Thanks Joe. v2 is now merged. Bruce On Mon, Apr 8, 2019 at 5:23 PM Joe Slater wrote: > > arch.h does not contain macros for 32 bit arm or any mips arch. > > Signed-off-by: Joe Slater > --- > recipes-extended/libibverbs/libibverbs_1.2.1.bb | 3 +++ > 1 file changed, 3 insertions(+) > > diff

Re: [oe] [meta-oe][PATCH] lvm2: Update source location

This was already sent yesterday: [oe] [meta-oe][PATCH] lvm2: update SRC_URI Cheers, Bruce On Fri, Nov 2, 2018 at 8:50 AM Hugues Kamba wrote: > > Signed-off-by: Hugues Kamba > --- > meta-oe/recipes-support/lvm2/lvm2.inc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [oe] [sumo] [meta-virtualization] [PATCH v1] docker: CVE-2018-10892

Wrong list. This needs to go to the meta-virtualization mailing list. Bruce On Thu, Oct 4, 2018 at 11:48 PM Sinan Kaya wrote: > > * CVE-2018-10892 > Docker does not block /proc/acpi pathnames. The flaw allows an attacker to > modify host's hardware like enabling/disabling Bluetooth or turning

Re: [oe] [meta-networking][PATCH] tgt: Migrate recipe from meta-openstack layer

On Sun, Jul 15, 2018 at 11:44 PM, Yu, Mingli wrote: > > > On 2018年07月14日 02:47, Khem Raj wrote: >> >> On 7/13/18 12:35 PM, Jagadeesh Krishnanjanappa wrote: >>> >>> Yes, we need to copy libconfig-general-perl recipe (from meta-openstack) >>> to >>> meta-networking as well. >>> >>> Bruce comment:

Re: [oe] [meta-networking][PATCH] tgt: Migrate recipe from meta-openstack layer

On Sat, Jul 7, 2018 at 4:54 PM, Bruce Ashfield wrote: > On Sat, Jul 7, 2018 at 1:25 PM, Jagadeesh Krishnanjanappa > wrote: >> As iscsitarget cannot be built with Linux kernel >= 4.14, so >> migrate Linux SCSI target framework (tgt) recipe from meta-openstack >> la

Re: [oe] [meta-networking][PATCH][master][sumo] iscsitarget: Remove recipe as it is no longer supported to build with linux kernel >= 4.14

On Fri, Jul 6, 2018 at 9:10 PM, akuster808 wrote: > > > On 07/06/2018 10:33 AM, Jagadeesh Krishnanjanappa wrote: >> The upstream iscsitarget source does not have support to build >> with Linux kernel >= 4.14, as the "struct bio" members has been updated >> in the linux kernel v4.14 source.

Re: [oe] [meta-networking][PATCH] tgt: Migrate recipe from meta-openstack layer

On Sat, Jul 7, 2018 at 1:25 PM, Jagadeesh Krishnanjanappa wrote: > As iscsitarget cannot be built with Linux kernel >= 4.14, so > migrate Linux SCSI target framework (tgt) recipe from meta-openstack > layer; to allow users to test iSCSI target feature with tgt in > meta-networking layer. What

Re: [oe] [PATCH] fix license from Apache-2.0 to MIT

On Fri, Jul 6, 2018 at 9:15 PM, akuster808 wrote: > > > On 07/05/2018 11:26 PM, Takuma Ueba wrote: >> Signed-off-by: Takuma Ueba >> --- >> meta-python/recipes-devtools/python/python-asn1crypto.inc | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git

Re: [oe] meta-bsp

On Tue, Apr 24, 2018 at 10:30 PM, Trevor Woerner wrote: > Hi, > > I'm tempted to reply to RP's "2.6 planning proposals and meeting" email > thread > to ask if there could be some support added for common BSP things, but I > have > a feeling it probably won't go down well.

Re: [oe] [meta-virtualization] runc update ftbfs on arm64

On 04/04/2018 05:18 AM, Fathi Boudra wrote: Hi Bruce, This commit https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=e3d960f4fcd91a84067fbbd6293ce271e74a7740 caused a build failure on arm64:

Re: [oe] [meta-virtualization] runc update ftbfs on arm64

On 2018-04-04 5:18 AM, Fathi Boudra wrote: Hi Bruce, This commit https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=e3d960f4fcd91a84067fbbd6293ce271e74a7740 caused a build failure on arm64:

Re: [oe] [meta-networking][PATCH V2 2/2] ebtables: Fix duplicate definition errors due to netinet/ether.h

FYI: I'm also about to spin a new linux-libc-headers that addresses this issue as well. There's a -stable patch that fixes the regression introduced in 4.15 headers, so I've bumped to 4.15.7 to pick up that fix. I also had to adjust the musl libc-headers patches for it slightly, but after those

Re: [oe] Splitting meta-oe?

On Thu, Mar 1, 2018 at 1:44 PM, akuster808 wrote: > > > On 03/01/2018 01:04 AM, Alexander Kanavin wrote: >> On 03/01/2018 03:17 AM, akuster808 wrote: >>> We had/have a situation with the Yocto 4.12 kernel that broke wireguard >>> in meta-networking. Their are two patches

Re: [oe] Splitting meta-oe?

d. I was just probing to see if anyone had ideas on how that could be managed by infrastructure, versus me mucking about. Maybe RP's thoughts on layer tooling or setup possibilities would help, but either way, I'll keep chugging along :D Cheers, Bruce > > -J. > >> >> On Wed,

Re: [oe] Splitting meta-oe?

On Wed, Feb 21, 2018 at 8:34 AM, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > On Wed, Feb 21, 2018 at 3:49 AM, Martin Jansa <martin.ja...@gmail.com> wrote: >>> I need an updated python- package for an unrelated package >> >> And how far will you go?

Re: [oe] Splitting meta-oe?

it is a valid concern .. whether or not others agree. Cheers, Bruce > > On Wed, Feb 21, 2018 at 1:51 AM, Bruce Ashfield <bruce.ashfi...@gmail.com> > wrote: >> >> On Tue, Feb 20, 2018 at 1:52 PM, Khem Raj <raj.k...@gmail.com> wrote: >> > On 2/20/18 9:13 AM, Bruce

Re: [oe] Splitting meta-oe?

On Tue, Feb 20, 2018 at 1:52 PM, Khem Raj <raj.k...@gmail.com> wrote: > On 2/20/18 9:13 AM, Bruce Ashfield wrote: >> On Tue, Feb 20, 2018 at 11:50 AM, akuster808 <akuster...@gmail.com> wrote: >>> >>> >>> On 02/20/2018 02:45 AM, Burton, Ross wrot

Re: [oe] Splitting meta-oe?

On Tue, Feb 20, 2018 at 11:50 AM, akuster808 wrote: > > > On 02/20/2018 02:45 AM, Burton, Ross wrote: >> Hi, >> >> Is now a good time to talk about splitting up meta-oe? Some layers are >> actively developed and maintained (one example: meta-python), others are >> basically

Re: [oe] [OE-core] Yocto vrs K.O kernel, wireguard go Boom

On Mon, Jan 8, 2018 at 4:57 PM, akuster808 <akuster...@gmail.com> wrote: > > > On 01/08/2018 08:01 AM, Bruce Ashfield wrote: > > > > On Mon, Jan 8, 2018 at 10:08 AM, akuster808 <akuster...@gmail.com> wrote: > >> Hello, >> >> Wireguard in met

Re: [oe] [OE-core] Yocto vrs K.O kernel, wireguard go Boom

On Mon, Jan 8, 2018 at 10:08 AM, akuster808 wrote: > Hello, > > Wireguard in meta-networking is failing do to compat.h issues on newer > kernels. I have updated the package and it fixed my problem on 4.14 K.O > kernel. Now I build it with the Yocko 4.12 and it fails. It

Re: [oe] [meta-oe][PATCH] vboxguestdrivers: update to fix build issues with 4.12+

On 08/29/2017 01:07 AM, Khem Raj wrote: On Mon, Aug 28, 2017 at 8:09 PM, Bruce Ashfield <bruce.ashfi...@windriver.com> wrote: Bumping the version to 5.1.26 fixes the build issues with the 4.12+ kernel (and headers). i.e.: tmp/work-shared/qemux86-64/kernel-source/arch/x86/inclu

Re: [oe] [meta-networking][PATCH] wireguard: fix kernel 4.12 build issues

On 08/29/2017 01:06 AM, Khem Raj wrote: On Mon, Aug 28, 2017 at 8:38 PM, Bruce Ashfield <bruce.ashfi...@windriver.com> wrote: We upgrade the module + tools recipes to fix the following build error: wireguard-module/0.0.20170517-r0/WireGuard-0.0.20170517/src/device.c: In function

[oe] [meta-networking][PATCH] wireguard: fix kernel 4.12 build issues

0.20170810-r0 do_package_qa: QA Issue: /usr/bin/wg-quick contained in package wireguard-tools requires /bin/bash, but no providers found in RDEPENDS_wireguard-tools? [file-rdeps] Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com> --- ...eguard-module_0.0.20170517.bb => wiregua

[oe] [meta-oe][PATCH] vboxguestdrivers: update to fix build issues with 4.12+

ror: undefined named operand 'new' | tmp/work-shared/qemux86-64/kernel-source/arch/x86/include/asm/atomic.h:192:2: error: undefined named operand 'new' Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com> --- .../{vboxguestdrivers_5.1.18.bb => vboxguestdrivers_5.1.26.bb}| 4

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2017-08-24

On Sat, Aug 26, 2017 at 1:59 PM, Martin Jansa wrote: > Issues in meta-qt5 caused by security_flags.inc were fixed in this round, for > next round I'll test fixed 5.9.0 upgrade and then final 5.9.2 upgrade. > > > Thanks for fixes for QA issues, few more are included in

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Mon, Apr 24, 2017 at 7:11 AM, Burton, Ross wrote: > > On 24 April 2017 at 11:29, Burton, Ross wrote: > >> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to >> update the BSP with some fixes you've made? >> > > Or ideally

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Mon, Apr 24, 2017 at 6:29 AM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 24 April 2017 at 01:31, Bruce Ashfield <bruce.ashfi...@gmail.com> > wrote: > >> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto >>> should be at a

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > > > On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross <ross.bur...@intel.com> > wrote: > >> On 16 April 2017 at 16:50, Khem Raj <raj.k...@gmail.com> wrote: >> >> >

Re: [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross wrote: > On 16 April 2017 at 16:50, Khem Raj wrote: > > > I have put together recipes for upcoming gcc-7 major release as well > > as glibc 2.26 release, which we would target for next release ( 2.4 ) > > >

[oe] [meta-filesystems][PATCH] aufs-utils-native: define CC

lready passed through. Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com> --- meta-filesystems/recipes-utils/aufs-util/aufs-util_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-filesystems/recipes-utils/aufs-util/aufs-util_git.bb b/meta-file

Re: [oe] [meta-networking][PATCH 2/2] dnsmasq: disable the service by default

it makes more sense. > > > > Thanks, > > Jackie > > > > *From:* Bruce Ashfield [mailto:bruce.ashfi...@gmail.com] > *Sent:* Monday, February 27, 2017 10:39 PM > *To:* Huang, Jie (Jackie) > *Cc:* openembedded-devel > *Subject:* Re: [oe] [meta-networking][PATCH 2/2]

Re: [oe] [meta-networking][PATCH 2/2] dnsmasq: disable the service by default

On Mon, Feb 27, 2017 at 3:09 AM, wrote: > From: Jackie Huang > > The service will fail to start/stop when dnsmasq and > bind (provides named) are both installed since they > are using the same port 53: > > | dnsmasq: failed to create

Re: [oe] [OE-core] [Openembedded-architecture] Removal of uclibc from oe-core?

On Mon, Jul 18, 2016 at 6:18 PM, Phil Blundell wrote: > On Mon, 2016-07-18 at 23:01 +0100, Burton, Ross wrote: > > > Now that musl is fairly mature I think it's time to take uclibc out to > > pasture, where the pasture is possibly called meta-uclibc. > > I think this is a splendid

Re: [oe] [PATCH 1/2] protobuf: add protobuf-c recipe

On Thu, Apr 28, 2016 at 4:02 AM, Felipe Ferreri Tonello < e...@felipetonello.com> wrote: > Hi Bruce, > > On 20/04/16 15:32, Bruce Ashfield wrote: > > On Wed, Apr 20, 2016 at 4:32 AM, Felipe Ferreri Tonello < > > e...@felipetonello.com> wrote: > > > >&

Re: [oe] [PATCH 1/2] protobuf: add protobuf-c recipe

On Wed, Apr 20, 2016 at 4:32 AM, Felipe Ferreri Tonello < e...@felipetonello.com> wrote: > Hi Bruce, > > On 19/04/16 20:55, Bruce Ashfield wrote: > > On Tue, Apr 19, 2016 at 3:46 PM, Bruce Ashfield < > bruce.ashfi...@gmail.com> > > wrote: > > >

Re: [oe] [PATCH 1/2] protobuf: add protobuf-c recipe

On Tue, Apr 19, 2016 at 3:46 PM, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > > > On Tue, Apr 19, 2016 at 11:40 AM, Felipe F. Tonello <e...@felipetonello.com> > wrote: > >> Initial version of recipe. The main package could be split into two to >> s

Re: [oe] [PATCH 1/2] protobuf: add protobuf-c recipe

On Tue, Apr 19, 2016 at 11:40 AM, Felipe F. Tonello wrote: > Initial version of recipe. The main package could be split into two to > separate the compiler. This also applies to protobuf recipe. > > More precisely, this is the initial version outside of

Re: [oe] [PATCH][meta-oe] virt-what: add the recipe

On Tue, Mar 29, 2016 at 4:22 AM, wrote: > From: Roy Li > > virt-what is a a shell script which can be used to detect if the program > is running in a virtual machine. > Did you consider meta-virtualization for this ? not a big concern ..

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2016-03-09

On Fri, Mar 11, 2016 at 11:13 AM, Martin Jansa <martin.ja...@gmail.com> wrote: > On Fri, Mar 11, 2016 at 10:52:14AM -0500, Bruce Ashfield wrote: > > On Fri, Mar 11, 2016 at 10:41 AM, Mark Hatle <mark.ha...@windriver.com> > > wrote: > > > > &

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2016-03-09

On Fri, Mar 11, 2016 at 10:41 AM, Mark Hatle wrote: > On 3/10/16 5:53 AM, Martin Jansa wrote: > > Aggressive PNBLACKLISTing continues. But linux-yocto (and modules > depending on it) > > are still broken :/. > > > > I'll look at cef3 and chromium issue, my recent patch

Re: [oe] [OE-core] linux-yocto issues Was: [meta-oe][PATCH] efivar: fix zero initializer compiler error

On Mon, Feb 1, 2016 at 5:45 AM, Martin Jansa wrote: > On Mon, Feb 01, 2016 at 11:24:03AM +0200, Alexandru But wrote: > > On Fri, Jan 29, 2016 at 07:01:57PM +0100, Martin Jansa wrote: > > > On Tue, Jan 19, 2016 at 12:45:18PM +0200, Alexandru But wrote: > > > > Patch based

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2016-01-09, full QA report

On 16-01-15 03:13 AM, Andrea Adami wrote: On Thu, Jan 14, 2016 at 1:21 PM, Martin Jansa wrote: qemuarm was using slightly older metadata, that's why it shows more failures. Reexecuting qemuarm build shows only one failure: Summary: 1 task failed:

Re: [oe] [OE-core] State of bitbake world, test-dependencies 2015-11-12

On Mon, Nov 16, 2015 at 10:11 AM, Martin Jansa wrote: > On Sat, Nov 14, 2015 at 10:57:39AM +0100, Martin Jansa wrote: >> On Thu, Nov 12, 2015 at 12:43:11PM +0100, Martin Jansa wrote: >> > Another incremental test, only 26 recipes were tested, but it found enough >> >

Re: [oe] [OE-core] kernel.bbclass: Fix do_shared_workdir task ordering

On Wed, Nov 11, 2015 at 4:00 AM, Jens Rehsack <rehs...@gmail.com> wrote: > >> Am 11.11.2015 um 03:01 schrieb Bruce Ashfield <bruce.ashfi...@gmail.com>: >> >> On Tue, Nov 10, 2015 at 4:33 AM, Jens Rehsack <rehs...@gmail.com> wrote: >>> >>>>

Re: [oe] [OE-core] kernel.bbclass: Fix do_shared_workdir task ordering

On Wed, Nov 11, 2015 at 9:59 AM, Jens Rehsack <rehs...@gmail.com> wrote: > >> Am 11.11.2015 um 13:49 schrieb Bruce Ashfield <bruce.ashfi...@gmail.com>: >> >> On Wed, Nov 11, 2015 at 4:00 AM, Jens Rehsack <rehs...@gmail.com> wrote: >>> >>>>

Re: [oe] [OE-core] kernel.bbclass: Fix do_shared_workdir task ordering

On Tue, Nov 10, 2015 at 4:33 AM, Jens Rehsack <rehs...@gmail.com> wrote: > >> Am 14.10.2015 um 21:48 schrieb Bruce Ashfield <bruce.ashfi...@gmail.com>: >> >> On Wed, Oct 14, 2015 at 3:30 PM, S. Lockwood-Childs <s...@vctlabs.com> wrote: >>&g

Re: [oe] [OE-core] kernel.bbclass: Fix do_shared_workdir task ordering

On Wed, Oct 14, 2015 at 3:30 PM, S. Lockwood-Childs wrote: > http://patchwork.openembedded.org/patch/99875/ > > Apparently this patch is still not in master, and I just ran across the > problem with an externally built module (omaplfb from omap3-sgx-modules) > in meta-ti layer.

Re: [oe] [meta-python][PATCH 3/4] python-msgpack: add recipe

On Thu, Feb 19, 2015 at 1:10 PM, Martin Jansa martin.ja...@gmail.com wrote: On Thu, Feb 19, 2015 at 12:42:49PM -0500, Bruce Ashfield wrote: On Thu, Feb 19, 2015 at 12:21 PM, Martin Jansa martin.ja...@gmail.com wrote: On Thu, Feb 19, 2015 at 12:09:09PM -0500, Bruce Ashfield wrote: On Wed

Re: [oe] [meta-python][PATCH 3/4] python-msgpack: add recipe

On Wed, Feb 18, 2015 at 6:03 PM, Ben Shelton ben.shel...@ni.com wrote: python-msgpack implements the MessagePack binary serialization format for Python. Copied from commit 91ed2353847d4121e3dd8ad10ca0c24194ac9765 in meta-cloud-services/meta-openstack and updated to version 0.4.5. Can you

Re: [oe] [meta-python][PATCH 4/4] python-requests: add recipe

On Wed, Feb 18, 2015 at 6:03 PM, Ben Shelton ben.shel...@ni.com wrote: Requests is an HTTP library for Python with a clean and succinct API. Copied from commit bc572006bfcec10523658b8675f30bf45b43a998 in meta-cloud-services/meta-openstack and updated to version 2.5.1. When you do this .. you

Re: [oe] [meta-python][PATCH 3/4] python-msgpack: add recipe

On Thu, Feb 19, 2015 at 12:21 PM, Martin Jansa martin.ja...@gmail.com wrote: On Thu, Feb 19, 2015 at 12:09:09PM -0500, Bruce Ashfield wrote: On Wed, Feb 18, 2015 at 6:03 PM, Ben Shelton ben.shel...@ni.com wrote: python-msgpack implements the MessagePack binary serialization format for Python

Re: [oe] [OE-core] What is expected of a kernel recipe nowadays?

On Tue, Jan 6, 2015 at 6:33 AM, Burton, Ross ross.bur...@intel.com wrote: On 6 January 2015 at 11:04, Martin Jansa martin.ja...@gmail.com wrote: | make: *** No rule to make target `oldconfig'. Stop. | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR:

Re: [oe] [PATCH] iscsi-initiator-utils: add recipe file

On 2014-09-24, 4:02 AM, Rongqing Li wrote: On 09/24/2014 03:37 PM, Rongqing Li wrote: I see there are two recipes for iscsi under meta-cloud-service, one is called iscsi-initiator-utils, other is called open-iscsi. and open-iscsi provides the systemd support and kernel modules, so I will

[oe] [meta-networking][PATCH 1/2] dnsmasq: uprev to 2.6.3

of PRSERVER functionality - dhcp_release is added to the default build, since it is used in the cleanup phase for virtual machines. Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com --- meta-networking/recipes-support/dnsmasq/dnsmasq.inc | 8 meta-networking/recipes

[oe] [meta-networking][PATCH 0/2]: meta-virtualization derived updates

of updating them for submission to meta-networking, and documented the tweaks in the patches themselves. Anyway, have a look, and let me know what additional changes you'd like made to the recipes. Cheers, Bruce Bruce Ashfield (2): dnsmasq: uprev to 2.6.3 netcf: move from meta-virtualization

[oe] [meta-networking][PATCH 2/2] netcf: move from meta-virtualization to meta-networking

netcf was orginally introduced in meta-virtualization, since it provides functionality required by libvirt, but it is otherwise not bound to virtualization. So we can move it to meta-networking, and in the process uprev to the the latest 0.2.3 functinality. Signed-off-by: Bruce Ashfield

[oe] [meta-oe][PATCH] python-greenlet: uprev to 0.4.1

During runtime testing of meta-cloud-services several python scripts were continunously segfaulting the interpreter. corefiles and gdb pointed at the greenlet implementation. Moving to 0.4.1 fixed the segfaults, and showed no regressions. Signed-off-by: Bruce Ashfield bruce.ashfi

[oe] [PATCH] python-greenlet: uprev to 0.4.1

During runtime testing of meta-cloud-services several python scripts were continunously segfaulting the interpreter. corefiles and gdb pointed at the greenlet implementation. Moving to 0.4.1 fixed the segfaults, and showed no regressions. Signed-off-by: Bruce Ashfield bruce.ashfi

  1   2   >