Re: [OE-core] [oe-commits] [openembedded-core] 01/36: expat: Don't use getrandom() in the -native case

On Tue, 2017-09-12 at 00:59 +0200, Martin Jansa wrote: > Was this tested with the version in pyro? The patch fails to apply: > > > http://errors.yoctoproject.org/Errors/Build/46432/ > > NOTE: Applying patch 'autotools.patch' (oe-core/meta/recipes- > core/expat/expat/autotools.patch) > NOTE: Appl

Re: [OE-core] [PATCH 0/2] python3-pip & python3-setuptools: extend to nativesdk

On 09/11/2017 11:07 PM, Burton, Ross wrote: These are in master-next. Ross Thanks Ross. There are three other patch series on the mailing list. Is it possible for these patches to get into this release? Or we need to wait for the development cycle for the next release? Their titles are: [O

[OE-core] [PATCH V2 0/1] ovmf: fix do_compile error when len(tmp)=410

Changed in V2: Add the MAX_LONG_FILE_PATH to 1023. The following changes since commit 8b4f16a9cbbaf521461f699b7264fac2ac872581: mesa-gl: Fix build after recent mesa PACKAGECONFIG changes (2017-09-05 15:01:02 +0100) are available in the git repository at: https://github.com/DengkeDu

[OE-core] [PATCH V2 1/1] ovmf: fix do_compile error when len(tmp)=410

[YOCTO #11354] Signed-off-by: Dengke Du --- .../ovmf/0004-ovmf-enable-long-path-file.patch | 28 ++ meta/recipes-core/ovmf/ovmf_git.bb | 3 ++- 2 files changed, 30 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-core/ovmf/ovmf/0004-ovmf-ena

Re: [OE-core] [PATCH 1/1] ovmf: fix do_compile error when len(tmp)=410

Ok, I will resend it with 1023. On 2017年09月11日 18:51, Burton, Ross wrote: On 11 September 2017 at 08:29, Dengke Du > wrote: +-#define MAX_LONG_FILE_PATH 500 ++#define MAX_LONG_FILE_PATH 800 Making this limit a little bigger seems like a great way to hi

Re: [OE-core] [PATCH] glibc-locale: add runtime dependency on glibc

On Mon, Sep 11, 2017 at 10:05 AM, Martin Jansa wrote: > * the libc.so.6 dependency is detected always: > $ grep FILERDEPENDS BUILD-*/pkgdata/qemux86/runtime/localedef > BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDSFLIST_localedef: > /usr/bin/localedef > > BUILD-bad/pkgdata/qemux

Re: [OE-core] [oe-commits] [openembedded-core] 01/36: expat: Don't use getrandom() in the -native case

Was this tested with the version in pyro? The patch fails to apply: http://errors.yoctoproject.org/Errors/Build/46432/ NOTE: Applying patch 'autotools.patch' (oe-core/meta/recipes-core/expat/expat/autotools.patch) NOTE: Applying patch 'no_getrandom.patch' (oe-core/meta/recipes-core/expat/expat/n

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On Tuesday, 12 September 2017 10:10:51 AM NZST Burton, Ross wrote: > On 11 September 2017 at 23:09, Martin Jansa wrote: > > > > Changing arch on a package resets the incrementing PR? Isn't that a > > bug? > > > > Arch is part of the key in PR server database. > > > > It's not a bug, because when

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On 11 September 2017 at 23:09, Martin Jansa wrote: > > Changing arch on a package resets the incrementing PR? Isn't that a > bug? > > Arch is part of the key in PR server database. > > It's not a bug, because when you have MACHINE_ARCH recipe then it's normal > that different MACHINEs (with diff

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

> Changing arch on a package resets the incrementing PR? Isn't that a bug? Arch is part of the key in PR server database. It's not a bug, because when you have MACHINE_ARCH recipe then it's normal that different MACHINEs (with different bbappends in BSP layers) have different EXTENDPRAUTO, witho

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On 11 September 2017 at 23:01, Otavio Salvador < otavio.salva...@ossystems.com.br> wrote: > On Mon, Sep 11, 2017 at 6:59 PM, Burton, Ross > wrote: > > On 11 September 2017 at 22:58, Otavio Salvador > > wrote: > >> > >> On Mon, Sep 11, 2017 at 6:49 PM, Burton, Ross > >> wrote: > >> > On 11 Septe

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On Mon, Sep 11, 2017 at 6:59 PM, Burton, Ross wrote: > On 11 September 2017 at 22:58, Otavio Salvador > wrote: >> >> On Mon, Sep 11, 2017 at 6:49 PM, Burton, Ross >> wrote: >> > On 11 September 2017 at 22:33, California Sullivan >> > wrote: >> >> >> >> Bump initramfs-framework PR, as it was mis

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On 11 September 2017 at 22:58, Otavio Salvador < otavio.salva...@ossystems.com.br> wrote: > On Mon, Sep 11, 2017 at 6:49 PM, Burton, Ross > wrote: > > On 11 September 2017 at 22:33, California Sullivan > > wrote: > >> > >> Bump initramfs-framework PR, as it was missed in the previous > >> initra

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On Mon, Sep 11, 2017 at 6:49 PM, Burton, Ross wrote: > On 11 September 2017 at 22:33, California Sullivan > wrote: >> >> Bump initramfs-framework PR, as it was missed in the previous >> initramfs-framework patch. > > > There's no need to bump PR. In the ideal world, the PR isn't assigned at > al

Re: [OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

On 11 September 2017 at 22:33, California Sullivan < california.l.sulli...@intel.com> wrote: > Bump initramfs-framework PR, as it was missed in the previous > initramfs-framework patch. > There's no need to bump PR. In the ideal world, the PR isn't assigned at all. Ross --

[OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

Bump initramfs-framework PR, as it was missed in the previous initramfs-framework patch. These modules are shell scripts so they can be allarch. Fix the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in layer.conf, as these dependencies moved from the main recipe to these modules. Finally, set the PR to 4 in t

[OE-core] [PATCH v7 2/2] kernel-devicetree.bbclass: Add support to generate append to kernel

The are use cases where the Device Tree appended to the kernel is convinient, so we generate the bundle concatenating the kernel (and potentionally the initramfs) and the Device Tree binaries. To enable it, set KERNEL_DEVICETREE_BUNDLE variable to '1' Signed-off-by: Otavio Salvador --- Changes

[OE-core] [PATCH v7 1/2] kernel: Move Device Tree support to kernel.bbclass

The Device Tree is commonly used but it is still kept as a .inc file instead of a proper class. Instead now we move the Device Tree code to a kernel-devicetree class and automatically enable it when the KERNEL_DEVICETREE variable is set. While converting to the class, we reworked the compile and i

Re: [OE-core] ✗ patchtest: failure for Revamp the Go support (rev7)

On Mon, Sep 11, 2017 at 4:53 PM, Leonardo Sandoval wrote: ... >> * Issue Added patch file is missing Upstream-Status in the >> header [test_upstream_status_presence] >> Suggested fixAdd Upstream-Status: to the header of >> meta/recipes-devtools/go/go-1.8/set-gotooldir-during-b

[OE-core] [PATCH] u-boot: Upgrade to 2017.09

This upgrades the U-Boot to the 2017.09 release. Signed-off-by: Otavio Salvador --- .../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimag

[OE-core] [PATCH v2 3/3] wic: apply --extra-space + --overhead to squashfs

The --extra-space and --overhead option did not had an effect to squashfs partitions. Although squashfs is read-only, it can be useful to allocate more space for the on-disk partition to avoid repartitioning of the whole disk when a new (and larger) squashfs image is written on later updates. Pat

Re: [OE-core] ✗ patchtest: failure for Revamp the Go support (rev7)

Patchwork writes: > == Series Details == > > Series: Revamp the Go support (rev7) > Revision: 7 > URL : https://patchwork.openembedded.org/series/8697/ > State : failure > > == Summary == > > > Thank you for submitting this patch series to OpenEmbedded Core. This is > an automated response. Sev

Re: [OE-core] [meta-oe][PATCH] gnupg: added a coreutils runtime dependancy to gnupg recipe

The error was */usr/bin/apt-key: line 352: comm: command not found* so, i investigated around this line and it showed me that apt-key script try to use* comm* in a function *merge_back_changes()* i couldn't find a suitable online source for the code, i just looked at from the resulted image. so as

[OE-core] ✗ patchtest: failure for Revamp the Go support (rev7)

== Series Details == Series: Revamp the Go support (rev7) Revision: 7 URL : https://patchwork.openembedded.org/series/8697/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the pro

[OE-core] [PATCH v7 11/12] go.bbclass: enable nativesdk builds for Go packages

From: Matt Madison Adding the necessary overrides for nativesdk builds. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v6: - new patch meta/classes/go.bbclass | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/classes/go.bbclass b/meta/

[OE-core] [PATCH v7 12/12] go-cross-canadian: add recipe

From: Matt Madison Enable cross-canadian builds of the Go toolchain. This requires an additional patch to the Go source to allow us to use the native GOTOOLDIR during the bootstrap phase. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: - Add patch header Change

[OE-core] [PATCH v7 10/12] go-crosssdk: add recipe

From: Matt Madison Enable crosssdk builds for the Go toolchain. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v6: - new patch meta/recipes-devtools/go/go-crosssdk.inc| 55 + meta/recipes-devtools/go/go-crosssdk_

[OE-core] [PATCH v7 08/12] go-cross: take GOARM environment setting

From: Matt Madison Instead of hard-coding GOARM to ${TARGET_GOARM} in the wrapper script, take it from an existing environment setting if present. This allows the same cross-compiler to be used for different ARM targets. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes

[OE-core] [PATCH v7 09/12] go: enable nativesdk builds for the toolchain

From: Matt Madison All that's needed is setting BBCLASSEXTEND. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v6: - new patch meta/recipes-devtools/go/go-target.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-devtools/go

[OE-core] [PATCH v7 06/12] go.bbclass: clean up CGO_xxx settings

From: Matt Madison * use conditional assignment for the CGO_xxx variables, so they can be overridden more easily * remove the TOOLCHAIN_OPTIONS and TARGET_CC_ARCH references, since those are already present in CC and CXX * remove the TARGET_ prefix so the values are appropriate for nativ

[OE-core] [PATCH v7 07/12] go: rename go.inc -> go-target.inc

From: Matt Madison to make it clearer that it is only used for building the toolchain for the target. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v6: - new patch meta/recipes-devtools/go/{go.inc => go-target.inc} | 0 meta/recipes-devtools/g

[OE-core] [PATCH v7 04/12] go.bbclass: remove GO_GCFLAGS nad GO_LDFLAGS

From: Matt Madison These variables are not used anywhere. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v6: - new patch meta/classes/go.bbclass | 2 -- 1 file changed, 2 deletions(-) diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbcl

[OE-core] [PATCH v7 05/12] go.bbclass: remove some xxx_FINAL variables

From: Matt Madison GOROOT_FINAL is used by the Go linker for rewriting source paths when the build GOROOT is not the same as the runtime GOROOT, but the other _FINAL variables aren't really needed. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v

[OE-core] [PATCH v7 02/12] go-bootstrap-native: remove recipe

From: Matt Madison No longer needed, with go-native handling its own bootstrap phase. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v7: None Changes in v6: - new patch meta/recipes-devtools/go/go-1.4.inc| 16 -- ...alignment-for-the-.rel.plt-sect

[OE-core] [PATCH v7 01/12] go-native: remove dependency on go-bootstrap-native

From: Matt Madison The go1.4 toolchain is only required for bootstrapping go-native, and should not be used for anything else, so build it as part of the go-native build. This way, we don't have to carry around its built artifacts in the native sysroot. The go-cross and target toolchains can the

[OE-core] [PATCH v7 03/12] go: split out go-runtime into separate recipe

From: Matt Madison Reorganize the Go toolchain build to split out the Go standard runtime libraries into a separate recipe. This simplifies the extension to crosssdk and cross-canadian builds. * Adds a patch to the go build tool to prevent it from trying to rebuild anything in GOROOT, which

[OE-core] [PATCH v7 00/12] Revamp the Go support

This improves the Go support on OE-Core. We are trying to port as much as possible work done by Matt on meta-golang back to OE-Core and also to avoid carrying old releases as there is no need to support more versions of Go toolchain. This fixes issues in existing support as well as add support fo

Re: [OE-core] [PATCH v3] initramfs-framework: split setup-live and install-efi into separate recipes

It looks like v1 was merged, so I'll have to rebase and send another patch. --- Cal On 09/09/2017 02:33 PM, Otavio Salvador wrote: On Fri, Sep 8, 2017 at 7:12 PM, California Sullivan wrote: Having these the initramfs-framework recipe forced initramfs-framework users to build several tools the

[OE-core] [PATCH] initramfs-framework: Allow directories with spaces

When mdev module loads the Linux kernel modules, it can visit directories with spaces. To allow that, we must quote the variable otherwise it misunderstand it arguments as multiple entries. Fixes: , | Freeing unused kernel memory: 3072K (80d0 - 8100) | cat: can't open '/sys/devices/pl

[OE-core] [PATCH] glibc-locale: add runtime dependency on glibc

* the libc.so.6 dependency is detected always: $ grep FILERDEPENDS BUILD-*/pkgdata/qemux86/runtime/localedef BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDSFLIST_localedef: /usr/bin/localedef BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDS_/usr/bin/localedef_localedef: li

Re: [OE-core] [PATCH 0/2] python3-pip & python3-setuptools: extend to nativesdk

These are in master-next. Ross On 11 September 2017 at 02:44, ChenQi wrote: > ping > > On 09/06/2017 12:54 PM, Chen Qi wrote: > >> The following changes since commit 8b4f16a9cbbaf521461f699b7264fa >> c2ac872581: >> >>mesa-gl: Fix build after recent mesa PACKAGECONFIG changes (2017-09-05 >>

[OE-core] Yocto Project Status WW37’17

Current Dev Position: YP 2.4 M4 Next Deadline: YP 2.4 Final Cut off is Sept. 18, 2017 SWAT team rotation: Tracy -> Alejandro on Sept. 8, 2017 SWAT team rotation: Alejandro -> Stephano on Sept. 15, 2017. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: ·

[OE-core] [PATCH] libarchive: fix bug929 and CVE-2017-14166

Signed-off-by: Andrej Valek --- .../libarchive/libarchive/CVE-2017-14166.patch | 37 + .../libarchive/libarchive/bug929.patch | 38 ++ .../libarchive/libarchive_3.3.2.bb | 2 ++ 3 files changed, 77 insertions(+) create mode

Re: [OE-core] [PATCH] iproute2: Default to tipc enabled, and include libmnl dependency

On 9/7/17 4:36 AM, Trevor Woerner wrote: > https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg101002.html Yes, but I feel this needs to be re-considered. At present we can't pass the Yocto Project compliant test (with meta-openembedded included) without enabling tipc for ipr

Re: [OE-core] [PATCH] psplash: Initialize psplash only if a framebuffer exists

On 9/6/17 8:31 AM, Mike Looijmans wrote: > Isn't this a weird situation? > > If you installed psplash but don't have a framebuffer, then something must be > broken. I'd rather see that error than this being silently ignored and then > wondering where the splash went. Sorry I missed this reply b

Re: [OE-core] [PATCH 3/3] wic: apply --extra-space + --overhead to squashfs

Ed Bartosh writes: >> The --extra-space and --overhead option did not had an effect to squashfs >> partitions. Although squashfs is read-only, it can be useful to allocate >> more space for the on-disk partition to avoid repartitioning of the whole >> disk when a new (and larger) squashfs image

Re: [OE-core] [PATCH 3/3] wic: apply --extra-space + --overhead to squashfs

On Fri, Sep 08, 2017 at 07:33:03PM +0200, Enrico Scholz wrote: > From: Enrico Scholz > > The --extra-space and --overhead option did not had an effect to squashfs > partitions. Although squashfs is read-only, it can be useful to allocate > more space for the on-disk partition to avoid repartitio

Re: [OE-core] hidraw support in the kernel(s)

On Mon, Sep 11, 2017 at 4:48 AM, Patrick Ohly wrote: > Hello! > > I am currently trying to get fwupd [1] working. For updating a Lenovo > Unifying Dongle (the USB thingie which connects to wireless mice and > keyboards), the kernel has to support hidraw, aka CONFIG_HIDRAW, > otherwise fwupd does

[OE-core] ✗ patchtest: failure for Revamp the Go support (rev6)

== Series Details == Series: Revamp the Go support (rev6) Revision: 6 URL : https://patchwork.openembedded.org/series/8697/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the pro

Re: [OE-core] [meta-oe][PATCH] gnupg: added a coreutils runtime dependancy to gnupg recipe

On 09/09/2017 01:17 AM, Yahia Farghaly wrote: From: yahiafarghaly When using 'apt-key add' on the target image, the gnupg is required but for gnupg to be fully functional, the coreutils is required to be exist with the gnupg. Otherwise, it may throw an error in runtime as one of components of

Re: [OE-core] [PATCH v2] kernel-module-split: rrecommend kernel-image instead of rdepend

On Mon, 2017-09-11 at 14:19 +0200, Martin Hundebøll wrote: > > On 2017-09-11 11:26, Richard Purdie wrote: > > > > On Mon, 2017-09-11 at 09:02 +0200, Martin Hundebøll wrote: > > >  > > > Reverting the patch is fine by me - sorry for the noise. > > Are you sure? I can't imagine being able to influe

[OE-core] [PATCH v5 23/26] go: enable nativesdk builds for the toolchain

From: Matt Madison All that's needed is setting BBCLASSEXTEND. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/recipes-devtools/go/go-target.inc | 3 +++ 1 file ch

[OE-core] [PATCH v5 24/26] go-crosssdk: add recipe

From: Matt Madison Enable crosssdk builds for the Go toolchain. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/recipes-devtools/go/go-crosssdk.inc| 55 +++

[OE-core] [PATCH v5 25/26] go.bbclass: enable nativesdk builds for Go packages

From: Matt Madison Adding the necessary overrides for nativesdk builds. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/classes/go.bbclass | 2 ++ 1 file changed,

[OE-core] [PATCH v5 26/26] go-cross-canadian: add recipe

From: Matt Madison Enable cross-canadian builds of the Go toolchain. This requires an additional patch to the Go source to allow us to use the native GOTOOLDIR during the bootstrap phase. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5

[OE-core] [PATCH v5 22/26] go-cross: take GOARM environment setting

From: Matt Madison Instead of hard-coding GOARM to ${TARGET_GOARM} in the wrapper script, take it from an existing environment setting if present. This allows the same cross-compiler to be used for different ARM targets. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes

[OE-core] [PATCH v5 21/26] go: rename go.inc -> go-target.inc

From: Matt Madison to make it clearer that it is only used for building the toolchain for the target. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/recipes-devto

[OE-core] [PATCH v5 20/26] go.bbclass: clean up CGO_xxx settings

From: Matt Madison * use conditional assignment for the CGO_xxx variables, so they can be overridden more easily * remove the TOOLCHAIN_OPTIONS and TARGET_CC_ARCH references, since those are already present in CC and CXX * remove the TARGET_ prefix so the values are appropriate for nativ

[OE-core] [PATCH v5 17/26] go: split out go-runtime into separate recipe

From: Matt Madison Reorganize the Go toolchain build to split out the Go standard runtime libraries into a separate recipe. This simplifies the extension to crosssdk and cross-canadian builds. * Adds a patch to the go build tool to prevent it from trying to rebuild anything in GOROOT, which

[OE-core] [PATCH v5 18/26] go.bbclass: remove GO_GCFLAGS nad GO_LDFLAGS

From: Matt Madison These variables are not used anywhere. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/classes/go.bbclass | 2 -- 1 file changed, 2 deletions(-)

[OE-core] [PATCH v5 19/26] go.bbclass: remove some xxx_FINAL variables

From: Matt Madison GOROOT_FINAL is used by the Go linker for rewriting source paths when the build GOROOT is not the same as the runtime GOROOT, but the other _FINAL variables aren't really needed. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Chan

[OE-core] [PATCH v5 16/26] go-bootstrap-native: remove recipe

From: Matt Madison No longer needed, with go-native handling its own bootstrap phase. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: - new patch Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/recipes-devtools/go/go-1.4.in

[OE-core] [PATCH v5 15/26] go-native: remove dependency on go-bootstrap-native

From: Matt Madison The go1.4 toolchain is only required for bootstrapping go-native, and should not be used for anything else, so build it as part of the go-native build. This way, we don't have to carry around its built artifacts in the native sysroot. The go-cross and target toolchains can the

[OE-core] [PATCH v5 13/26] go-dep: Add 0.3.0 release

This is the Golang dependency management tool under development; it is ready for production use and intended to be merged onto Golang 1.10. Until that, projects are starting to use it and making it available on OE-Core reduces the Golang integration work for new recipes. Signed-off-by: Otavio Salv

[OE-core] [PATCH v5 14/26] go-helloworld: Use the Golang examples repository

This updates the recipe to use the Golang examples repository so it makes use of the unpack as well as standard tasks showing how easy it can be. Signed-off-by: Otavio Salvador --- Changes in v6: None Changes in v5: - new patch Changes in v4: None Changes in v3: None Changes in v2: None .../g

[OE-core] [PATCH v5 12/26] go.bbclass: add GO_INSTALL_FILTEROUT variable

From: Matt Madison When using the Go 'vendor' mechanism to bring in dependencies for a Go package, the default GO_INSTALL setting, which uses the '...' wildcard, will include the vendored packages in the build, which produces incorrect results. There are also some Go packages that are structured

[OE-core] [PATCH v5 08/26] go.bbclass: exported function cleanup

From: Matt Madison Since this is a class, it should follow the class function export mechanism for its task functions, and should set directory-related flags for directories they need. Signed-off-by: Matt Madison Signed-off-by: Otavio Salvador --- Changes in v6: None Changes in v5: None Chang

[OE-core] [PATCH v5 11/26] go.bbclass: add do_unpack function to handle common cases

From: Matt Madison Go source trees have a particular structure, with all sources located under ${GOROOT}/src/. The fetcher step implemented by the 'go get' command automatically follows this structure, so we need to do the same here. Since most Go packages are hosted in git repositories, this ad

[OE-core] [PATCH v5 10/26] go.bbclass: separate ${S} and ${B}

From: Matt Madison Add a do_configure task to populate ${B} by symlinking in the src subdirectory under ${S}, which lets us point GOPATH at ${B}. This lets us take advantage of the automatic directory creation and cleaning for do_configure. This necessitates a change to do_install to split the

[OE-core] [PATCH v5 09/26] go.bbclass: Use an auxiliary variable to add the build dependencies

This is going to easy the addition of nativesdk and virtual providers in the future. This change is based on the meta-golang[1] layer. Thanks to Matt Madison for his work on this. 1. https://github.com/madisongh/meta-golang Signed-off-by: Otavio Salvador --- Changes in v6: None Changes in v5:

[OE-core] [PATCH v5 06/26] go.bbclass: Use a global Go build flags

We now use a GOBUILDFLAGS to provide a global variable to control the build flags to be given to Go. This change is based on the meta-golang[1] layer. Thanks to Matt Madison for his work on this. 1. https://github.com/madisongh/meta-golang Signed-off-by: Otavio Salvador --- Changes in v6: Non

[OE-core] [PATCH v5 05/26] goarch.bbclass: Add support for ARMv5

This adds support to return the proper ARMv5 format. This change is based on the meta-golang[1] layer. Thanks to Matt Madison for his work on this. 1. https://github.com/madisongh/meta-golang Signed-off-by: Otavio Salvador --- Changes in v6: None Changes in v5: None Changes in v4: - rebase on

[OE-core] [PATCH v5 04/26] goarch.bbclass: Replace logic for setting GOARM

From: Will Newton The previous logic applied a regex to TUNE_FEATURES which could set the GOARM value to 7 incorrectly, for example when dealing with an arm1176 core. Simplify to check for the presence of "armv7" instead. At the same time add a check for "armv6" and set GOARM to 6 in that case.

[OE-core] [PATCH v5 07/26] go.bbclass: Enable parallel build

The parallel build is based on PARALLEL_MAKE variable but can be overriden setting the GO_PARALLEL_BUILD one. This change is based on the meta-golang[1] layer. Thanks to Matt Madison for his work on this. 1. https://github.com/madisongh/meta-golang Signed-off-by: Otavio Salvador --- Changes i

[OE-core] [PATCH v5 03/26] go: Remove Go 1.6 and 1.7 releases

The OE-Core has no reason to support multiple versions of Go as this increases the maintenance work and testing efforts. So we are going to support just a single version from now on which currently is 1.8.3. The 1.4 release is kept around as it is used for bootstrap, as such, it cannot be removed.

[OE-core] [PATCH v5 02/26] go.bbclass: Fix binary installation path detection

Go toolchain changes the installation path when building for the same architecture as the build host. This was already been considered in the GO_BUILD_BINDIR variable but was not being used by the go class. This fixes following error: , | ERROR: go-dep-0.3.0-r0 do_package: QA Issue: go-dep: F

[OE-core] [PATCH v5 01/26] goarch.bbclass: Stop passing True as second argument of d.getVar

The d.getVar has the second argument as True by default, avoid passing it here. Signed-off-by: Otavio Salvador --- Changes in v6: None Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: None meta/classes/goarch.bbclass | 18 +- 1 file changed, 9 insertio

[OE-core] [PATCH v5 00/26] Revamp the Go support

This improves the Go support on OE-Core. We are trying to port as much as possible work done by Matt on meta-golang back to OE-Core and also to avoid carrying old releases as there is no need to support more versions of Go toolchain. This fixes issues in existing support as well as add support fo

[OE-core] [PATCHv2] Revert "kernel-module-split: rrecommend kernel-image instead of rdepend"

This reverts commit e0ed52c51464855e9a6a37ea49df7efde7e91076. Commit e0ed52c514 ('kernel-module-split: rrecommend kernel-image instead of rdepend') changed kernel modules to rrecommend kernel-image instead of rdepend on kernel. This broke existing setups, where the kernel is omitted by setting RDE

Re: [OE-core] [PATCH v2] kernel-module-split: rrecommend kernel-image instead of rdepend

On 2017-09-11 11:26, Richard Purdie wrote: On Mon, 2017-09-11 at 09:02 +0200, Martin Hundebøll wrote: On 2017-09-08 23:29, Paul Barker wrote: On Fri, Sep 8, 2017 at 10:07 PM, Martin Hundebøll wrote: No, you'd need it to be set in a conf file so it takes effect when the kernel-base pa

[OE-core] [PATCH][V2] staging: gracefully abort if two recipes conflict in the sysroot

When building the per-recipe sysroot keep track of what files we're installing and where they came from, so we can detect when a file is installed by two different recipes and tell the user what these recipes are (instead of just showing a os.link() stack trace). [ YOCTO #11631 ] (From OE-Core re

[OE-core] [PATCH] hostap-utils: use w1.fi for SRC_URI

epitest.fi is down and hostap-utils source is now available in w1.fi. So, move SRC_URI to https://w1.fi Since hostap-utils is only meant for old Intersil Prism2/2.5/3 wifi cards, this recipe will be removed from oe-core in future (most likely to meta-handheld) [YOCTO #12051] Signed-off-by: Maxin

Re: [OE-core] [PATCH 1/1] ovmf: fix do_compile error when len(tmp)=410

On 11 September 2017 at 08:29, Dengke Du wrote: > +-#define MAX_LONG_FILE_PATH 500 > ++#define MAX_LONG_FILE_PATH 800 > Making this limit a little bigger seems like a great way to hit it with a slightly longer path. The other patch (VfrCompile-increase-path-length-limit.patch) increases it to 1

Re: [OE-core] [PATCH 1/2] runqemu: default qemumips memory to 256M

On 11 September 2017 at 10:28, Robert Yang wrote: > The qemumips or qemumips64 can't be boot with 512M. > > *Fixed when no QB_MEM is set: > - runqemu qemumips nographic core-image-minimal > [0.00] Call Trace: > [0.00] [<8011c010>] clear_page+0x0/0x128 > [0.00] [<8022b818>

[OE-core] [PATCH 2/2] runqemu: let qemuparams override previous settings

Fixed: $ runqemu qemux86-64 qemuparams="-cpu coreduo" The default cpu is core2duo, but coreduo should be used here. Append qemuparams to the last can fix the problem. [YOCTO #11773] Signed-off-by: Robert Yang --- scripts/runqemu | 17 - 1 file changed, 12 insertions(+), 5 delet

[OE-core] [PATCH 0/2] runqemu: two fixes

The following changes since commit cc319b6dcc5b4a5019fb91c9771b12ce17f3c953: mesa-gl: Fix build after recent mesa PACKAGECONFIG changes (2017-09-05 14:58:37 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/qemu http://cgit.openembedde

[OE-core] [PATCH 1/2] runqemu: default qemumips memory to 256M

The qemumips or qemumips64 can't be boot with 512M. *Fixed when no QB_MEM is set: - runqemu qemumips nographic core-image-minimal [0.00] Call Trace: [0.00] [<8011c010>] clear_page+0x0/0x128 [0.00] [<8022b818>] get_page_from_freelist+0xa1c/0xb48 [0.00] [<8022c00c>]

Re: [OE-core] [PATCH v2] kernel-module-split: rrecommend kernel-image instead of rdepend

On Mon, 2017-09-11 at 09:02 +0200, Martin Hundebøll wrote: > > On 2017-09-08 23:29, Paul Barker wrote: > > > > On Fri, Sep 8, 2017 at 10:07 PM, Martin Hundebøll > > wrote: > > > > > >  > > No, you'd need it to be set in a conf file so it takes effect when > > the > > kernel-base package is crea

Re: [OE-core] [meta-oe][PATCH] gnupg: added a coreutils runtime dependancy to gnupg recipe

Not quite. What Khem was aiming for was to modify the packaging of coreutils so that individual binaries end up in their own packages. Currently this is not done for any of the coreutil binaries, but if you look at, e.g., util-linux, you will see this setup for quite a number of its utils. Howe

Re: [OE-core] [PATCH 0/4] Recipes for Open Source Verilog and Lattice iCE40 FPGAs tools

On 10 September 2017 at 14:14, Nathan Rossi wrote: > Please note whilst this series is sent for oe-core it may be better > located in another layer? (e.g. meta-oe). However since the recipes and > the tools they build are not specific to a single BSP it did not make > sense to keep in a BSP speci

[OE-core] hidraw support in the kernel(s)

Hello! I am currently trying to get fwupd [1] working. For updating a Lenovo Unifying Dongle (the USB thingie which connects to wireless mice and keyboards), the kernel has to support hidraw, aka CONFIG_HIDRAW, otherwise fwupd does not find the dongle. http://www.signal11.us/oss/udev/ is an artic

Re: [OE-core] [PATCH] Revert "kernel-module-split: rrecommend kernel-image instead of rdepend"

On Mon, Sep 11, 2017 at 8:23 AM, Martin Hundebøll wrote: > This reverts commit e0ed52c51464855e9a6a37ea49df7efde7e91076. > > Commit e0ed52c514 ('kernel-module-split: rrecommend kernel-image instead > of rdepend') changed kernel modules to rrecommend kernel-image instead > of rdepend on kernel. Thi

[OE-core] [PATCH] python-nose: Add HOMEPAGE info into recipe file.

Signed-off-by: Huang Qiyu --- meta/recipes-devtools/python/python-nose_1.3.7.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/python/python-nose_1.3.7.bb b/meta/recipes-devtools/python/python-nose_1.3.7.bb index 3757f3a..9b3509c 100644 --- a/meta/recipes-devtools/pyth

[OE-core] [PATCH] python-mako: Add HOMEPAGE info into recipe file.

Signed-off-by: Huang Qiyu --- meta/recipes-devtools/python/python-mako.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/python/python-mako.inc b/meta/recipes-devtools/python/python-mako.inc index ba50675..1c83af6 100644 --- a/meta/recipes-devtools/python/python-mako.

[OE-core] [PATCH 1/1] ovmf: fix do_compile error when len(tmp)=410

[YOCTO #11354] Signed-off-by: Dengke Du --- .../ovmf/0004-ovmf-enable-long-path-file.patch | 28 ++ meta/recipes-core/ovmf/ovmf_git.bb | 3 ++- 2 files changed, 30 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-core/ovmf/ovmf/0004-ovmf-ena

[OE-core] [PATCH 0/1] ovmf: fix do_compile error when len(tmp)=410

The following changes since commit 8b4f16a9cbbaf521461f699b7264fac2ac872581: mesa-gl: Fix build after recent mesa PACKAGECONFIG changes (2017-09-05 15:01:02 +0100) are available in the git repository at: https://github.com/DengkeDu/openembedded-core.git dengke/fix-ovmf-do-compile-error-whe

[OE-core] [PATCH] Revert "kernel-module-split: rrecommend kernel-image instead of rdepend"

This reverts commit e0ed52c51464855e9a6a37ea49df7efde7e91076. Commit e0ed52c514 ('kernel-module-split: rrecommend kernel-image instead of rdepend') changed kernel modules to rrecommend kernel-image instead of rdepend on kernel. This broke existing setups, where the kernel is omitted by setting RDE

Re: [OE-core] [PATCH v2] kernel-module-split: rrecommend kernel-image instead of rdepend

On 2017-09-08 23:29, Paul Barker wrote: On Fri, Sep 8, 2017 at 10:07 PM, Martin Hundebøll wrote: On September 8, 2017 10:37:26 PM GMT+02:00, Denys Dmytriyenko wrote: On Fri, Sep 08, 2017 at 09:06:17PM +0100, Paul Barker wrote: This breaks the method described in the kernel dev FAQ to o