On Tue, Feb 27, 2018 at 9:36 AM, Matt Madison wrote:
> New in v2:
> * Fixed Upstream-Status line in go patches
> * Added GOTMPDIR to do_configure[dirs]
>
> Updates to the go recipes and bbclasses for go1.10, which
> moves the bulk of the toolchain bootstrap and build
Hi Peter,
On Tue, Feb 27, 2018 at 03:23:32PM +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> > Maxin B. John
> > Sent: den 27 februari 2018 13:37
Upgrade to revision:
4ce0887e2f7f848d2be2e435a2d0f3c80e44ea3b
remove backported patch:
0001-tests-egl-egl-context-priority.c-Use-piglit_egl_get_.patch
Signed-off-by: Maxin B. John
---
...gl-context-priority.c-Use-piglit_egl_get_.patch | 41 --
Well, there is a benefit in having a common naming for layers in that it is
possible to easily identify them programmatically. E.g., our setup will
automatically take all checked out layers named “meta*” and add them to the
bblayers.conf.sample file. That said, the name “meta” as it has been
On Fri, Feb 23, 2018 at 10:48 PM, Denys Dmytriyenko wrote:
> On Thu, Feb 22, 2018 at 12:37:44PM -0800, akuster808 wrote:
> > I think openembededd-core is incorrect. it should have been
> > meta-openbedded-core or meta-core.
>
> It does have a layer called just "meta" though...
>
Add missing Upstream-Status to the following patch:
0001-WebKitMacros-Append-to-I-and-not-to-isystem.patch
Upstream-Status is fetched from the first commit of the patch:
commit id: 700b846ba0e0f31b06459aee3ebb3ce5f1715918
Signed-off-by: Maxin B. John
---
The result of running dbus-test-ptest was a series of
various segfaults, interpreted as FAILs. This was a direct consequence
of the test suite loading the installed shared library libdbus-1.so, not the
one built along the test suite.
While we normally want to test against the installed libraries,
atm, 'oe-init-build-env' expects 'bitbake' to be within the OE core git
repository. This complicates the project setup because you have to
manage the 'bitbake' directory or symlink manually (or specify the
bitbake location explicitly).
Looking for 'bitbake' outside the main git repository will
On 02/27/2018 01:46 AM, Anuj Mittal wrote:
Hi Cal,
On 02/27/2018 04:12 AM, California Sullivan wrote:
Since kernels will not necessarily be installed as vmlinuz anymore,
don't assume that's its name for either the bootloader config or the
copy of the kernel.
Also, allow installing multiple
Create a common function for locating task manifest files rather than
several implementations with missing pieces.
Signed-off-by: Richard Purdie
---
meta/classes/staging.bbclass | 36 +---
meta/lib/oe/package_manager.py | 31
Currently do_rootfs gets to see all rpms in the deploy directory. This filters
that view to only rpms which the image recipe has actual depends upon which
potentially removes some sources of confusion in the image construction.
This makes builds more reproducibile and also fixes contamination
Hi Cal,
On 02/27/2018 04:12 AM, California Sullivan wrote:
> Since kernels will not necessarily be installed as vmlinuz anymore,
> don't assume that's its name for either the bootloader config or the
> copy of the kernel.
>
> Also, allow installing multiple kernels by searching for common kernel
On Tue, Feb 27, 2018 at 5:56 AM, Anuj Mittal wrote:
...
> +++
> b/meta/recipes-multimedia/gstreamer/files/add-a-target-to-compile-tests.patch
> @@ -0,0 +1,61 @@
> +From 442691c7778601e3e4b88d0fbfb9d512ed34f414 Mon Sep 17 00:00:00 2001
> +From: Anuj Mittal
On 02/27/2018 05:38 PM, Otavio Salvador wrote:
> On Tue, Feb 27, 2018 at 5:56 AM, Anuj Mittal wrote:
> ...
>> +++
>> b/meta/recipes-multimedia/gstreamer/files/add-a-target-to-compile-tests.patch
>> @@ -0,0 +1,61 @@
>> +From 442691c7778601e3e4b88d0fbfb9d512ed34f414 Mon Sep
Make sure that the tests are packaged and can be executed
when ptest is enabled. Also, remove build host specific references
from Makefile.
Signed-off-by: Anuj Mittal
---
.../files/add-a-target-to-compile-tests.patch | 61 ++
Upgrade to revision:
4ce0887e2f7f848d2be2e435a2d0f3c80e44ea3b
remove backported patch:
0001-tests-egl-egl-context-priority.c-Use-piglit_egl_get_.patch
Signed-off-by: Maxin B. John
i# Your branch is ahead of 'origin/master' by 2 commits.
Signed-off-by: Maxin B.
1. Split package into libinput and libinput-tools.
2. Since libinput-tools contains python3 scripts, set RDEPENDS to python3
3. Fix a QA error related to python3 path:
a) 0001-libinput-measure-touchpad-tap-fix-python-script-QA-e.patch
Signed-off-by: Maxin B. John
1. Remove upstreamed patch:
0001-signpost-Add-paranthesis-to-remove-doubt-about-prece.patch
2. Bump PE to prevent version going backwards
3. LICENSE checksum change is due to Standardization of character
encoding of source tree on UTF-8.
Signed-off-by: Maxin B. John
* Patches and recipes reworked for go 1.10's significant
changes to its bootstrap and build steps
* Update go1.4 source tarball used for go-native
bootstrapping to the version recommended
in the current go documentation
* Remove test data from installed sources to eliminate
some
New in v2:
* Fixed Upstream-Status line in go patches
* Added GOTMPDIR to do_configure[dirs]
Updates to the go recipes and bbclasses for go1.10, which
moves the bulk of the toolchain bootstrap and build out
of the 'make.bash' script and to the 'dist' tool. This
required a rework of the
While useful on embedded devices for saving disk space, use
of shared runtime in Go is not the usual practice, so disable
it for nativesdk builds. We don't use it for native builds,
either, so this makes the SDK match the native environment
more closely.
Signed-off-by: Matt Madison
Eliminate some redundancy in the recipes by moving
some commonly-used variable settings to the common
include file.
Signed-off-by: Matt Madison
---
meta/recipes-devtools/go/go-common.inc | 4
meta/recipes-devtools/go/go-cross-canadian.inc | 5 -
* Don't enable verbose test output (-test.v)
by default, as it generates too much noise
for automated results parsing
* Override do_install_ptest_base in the bbclass,
so recipes can provide their own modifications
with do_install_ptest.
* Improve the generated run-ptest script to better
Go 1.10 adds support for selecting hard/soft float
object code through the GOMIPS environment variable.
Signed-off-by: Matt Madison
---
meta/classes/goarch.bbclass| 11 +++
meta/recipes-devtools/go/go-cross-canadian.inc | 1 +
The 'go env' in the do_compile function and
the set -x/+x in the do_install_ptest function
were used for debugging the bbclass, and aren't
really needed.
Signed-off-by: Matt Madison
---
meta/classes/go.bbclass | 3 ---
1 file changed, 3 deletions(-)
diff --git
Any directory in a Go package's source tree called
'testdata' contains test data, and isn't necessary
for building.
Some packages include ELF files and other binaries
as test data, and staging them in the sysroot and
-dev package leads to unnecessary QA warnings.
Signed-off-by: Matt Madison
and export it. Go 1.10 now supports using this
separate variable locating its temporary files,
so TMPDIR doesn't have to be modified.
Signed-off-by: Matt Madison
---
meta/classes/go.bbclass | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git
== Series Details ==
Series: "libinput: upgrade to version 1..." and 2 more (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/10793/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests
License-Update: checksum change is due to standardization of
character encoding of source tree on UTF-8
1. Remove upstreamed patch:
0001-signpost-Add-paranthesis-to-remove-doubt-about-prece.patch
2. Bump PE to prevent version going backwards
Signed-off-by: Maxin B. John
When installing the SDK to a non-default path, running "rpm --showrc" from the
sdk will produce the following error:
error: Unable to open
/opt/poky/2.4+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/rpm/rpmrc for
reading: No such file or directory.
Fix this by adding wrappers that dynamically
On 9 February 2018 at 07:03, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> gtk-doc recipe does have a direct dependency on python3-six, subject to
> 'api-documentation' in DISTRO_FEATURES. The reason it's conditional is that
> we don't want to build a ton of gtk-doc dependencies
On 2/27/18 8:09 AM, Alexander Kanavin wrote:
> On 02/27/2018 03:45 PM, Ovidiu Panait wrote:
>> +do_install_append_class-nativesdk() {
>> +tools="\
>> +${bindir}/rpm \
>> +${bindir}/rpm2archive \
>> +${bindir}/rpm2cpio \
>> +
On 02/27/2018 03:45 PM, Ovidiu Panait wrote:
+do_install_append_class-nativesdk() {
+tools="\
+${bindir}/rpm \
+${bindir}/rpm2archive \
+${bindir}/rpm2cpio \
+${bindir}/rpmbuild \
+${bindir}/rpmdb \
+
The following changes since commit 1b7a9d4f63d07d61d53daac12da275e8ef2feb24:
buildhistory-diff: honour report_all flag (2018-02-24 10:35:59 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/systemd-236
We should use the value of CC for the c compiler setting in cross
compilation configuration file for meson. For example, if we only
use ${HOST_PREFIX}gcc instead of ${CC}, we would meet the following
do_compile failure for systemd.
cc1: fatal error: linux/capability.h: No such file or directory
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Maxin B. John
> Sent: den 27 februari 2018 13:37
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 2/3] piglit:
Is it specific and/or limited to RPMs? How about other package managers?
On Tue, Feb 27, 2018 at 07:56:44PM +, Richard Purdie wrote:
> Currently do_rootfs gets to see all rpms in the deploy directory. This filters
> that view to only rpms which the image recipe has actual depends upon which
On Tue, 2018-02-27 at 16:36 -0500, Denys Dmytriyenko wrote:
> Is it specific and/or limited to RPMs? How about other package
> managers?
The code currently only does this for rpm, in theory it can easily be
reused by the other package managers too though.
I'd happily take patches which do this
Describes the new wildcard syntax in the documentation
Signed-off-by: Joshua Watt
---
documentation/ref-manual/ref-variables.xml | 18 ++
1 file changed, 18 insertions(+)
diff --git a/documentation/ref-manual/ref-variables.xml
From: Christopher Larson
buildhistory was writing srcrevs.values() as SRCREV when only one
srcrev/branch exists. This returns a view of the dictionary values in python
3, and used to return a list in python 2, neither of which is an appropriate
value for SRCREV. It was
Upgrade mesa form 17.3.5 to 17.3.6.
Signed-off-by: HuangQiyu
---
meta/recipes-graphics/mesa/{mesa-gl_17.3.5.bb => mesa-gl_17.3.6.bb} | 0
meta/recipes-graphics/mesa/{mesa_17.3.5.bb => mesa_17.3.6.bb} | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
Integrating the following fixes for yaffs2:
9f9649fffac9 yaffs2: Adjust the timer callback and init functions
0ef24a829eee yaffs2: include rawnand.h instead of nand.h
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
The existing kernel-devsrc package starts with a full copy of the kernel
source and then starts to strip out elements that are not required.
This results in extra time (I/O) and extra space being taken up in the
final package. The main purpose of the kernel-devsrc package has been to
build
Hi all,
I have some more -stable changes queued for the kernels, but didn't want
to sit on these any longer, in particulare the re-work of kernel-devsrc
to not suck up hundreds of megs, or hundreds of seconds of processing.
The 4.12 update is a feature addition, while 4.14/4.15 are yaffs2
Integrating the patches to introduce support for stratix10 SOC, which
comprises the following commits:
22f73c1fe991 drivers: ethernet: stmmac: keep Ethernet clock in enable status
on Stratix10 platform
c3ceae6df341 drivers: ethernet: stmmac: improve phy control during ethernet
Make sure that the tests are packaged and can be executed
when ptest is enabled. Also, remove build host specific references
from Makefile.
Signed-off-by: Anuj Mittal
---
.../files/add-a-target-to-compile-tests.patch | 61 ++
I wasn't able to get to this today for my v2. If this makes it in before
feature freeze I will open a bug and fix it before m4.
Thanks,
Cal
On 02/27/2018 01:15 PM, Cal Sullivan wrote:
On 02/27/2018 01:46 AM, Anuj Mittal wrote:
Hi Cal,
On 02/27/2018 04:12 AM, California Sullivan wrote:
This part is useful on its own, whereas the whole class together is
specific for image-live.
Signed-off-by: California Sullivan
---
.../{grub-efi.bbclass => grub-efi-cfg.bbclass} | 40 ---
meta/classes/grub-efi.bbclass | 122
This makes use of the grub-efi-cfg bbclass that was split out to create
a grub.cfg file just like the old one.
Signed-off-by: California Sullivan
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 29 +
1 file changed, 29 insertions(+)
EFI images require a boot partition containing the bootloader, the
kernel, the bootloader configuration, and any other EFI binaries that
your platform needs. Currently, the boot partition is done at image
creation time rather than through packages, making it very difficult to
add to its contents.
Since /boot/ will be recipe/package controlled now we can't just deploy.
Signed-off-by: California Sullivan
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 2 +-
meta/recipes-bsp/grub/grub-efi_2.02.bb | 34 +++--
2 files changed,
Rather than renaming the kernel to vmlinuz and assuming the name is
vmlinuz in the grub.cfg, copy to ${KERNEL_IMAGETYPE} and also use that
value in the grub.cfg file.
Signed-off-by: California Sullivan
---
meta/classes/grub-efi-cfg.bbclass | 4 +++-
I can't find VM_DEFAULT_KERNEL used anywhere else, and we should not be
statically installing the kernel as vmlinuz.
Signed-off-by: California Sullivan
---
meta/classes/live-vm-common.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff
Since the bootloader is now installed instead of added at image creation
time, this is necessary for booting.
Also set the default to grub-efi. This is done because a default of
grub-efi is already used by live-vm-common.bbclass, and in the event
that EFI_PROVIDER isn't defined errors would
This way we could theoretically support multiple bootloaders, and we
keep the convention of boot(x64|ia32).
Signed-off-by: California Sullivan
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff
We can't guarantee vmlinuz anymore. Use KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan
---
meta/classes/systemd-boot-cfg.bbclass | 6 +-
meta/classes/systemd-boot.bbclass | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git
We can't guarantee the kernel will be named vmlinuz anymore. Use
KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan
---
meta/classes/syslinux.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/syslinux.bbclass
Reuses our systemd-boot-cfg bbclass to generate systemd-boot
configuration files.
Signed-off-by: California Sullivan
---
meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 31 ++
1 file changed, 31 insertions(+)
create mode 100644
Previously this wasn't needed because the kernel was added at image
creation time to the boot partition. Now that the boot partition is
created from the /boot/ partition of the rootfs, it needs to be
installed there.
Signed-off-by: California Sullivan
---
Using --exclude-path and a wks.in file we can create an image that takes
the /boot/ directory for the boot partition, has an empty /boot/
directory in the rootfs partition. The boot partition gets mounted to
/boot/ after startup.
Signed-off-by: California Sullivan
We can no longer rely on the kernel having a static name of "vmlinuz".
This means we can't use it as a sentinel value in our sed commands, and
we can't just copy vmlinuz to the boot directory.
Instead, we'll use "root=" as the sentinel value for our sed commands,
and we'll search for common
Since kernels will not necessarily be installed as vmlinuz anymore,
don't assume that's its name for either the bootloader config or the
copy of the kernel.
Also, allow installing multiple kernels by searching for common kernel
names.
Signed-off-by: California Sullivan
The bootloaders depend on these to be functional in the non-deploy case,
but changes in them don't require rebuilding of the packages.
Signed-off-by: California Sullivan
---
meta/conf/layer.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git
If the EFI_PROVIDER is systemd-boot, install as boot(x64|ia32) as per
convention. If its not the EFI_PROVIDER, install as
systemd-boot(x64|ia32), as to not collide with other possible
bootloaders.
Signed-off-by: California Sullivan
---
Simple test case that adds 'efi' to MACHINE_FEATURES, sets WKS_FILE to
"efi-bootdisk.wks.in", installed required boot items, and attempts to
boot the wic image.
Quick check to make sure that the feature actually works.
Signed-off-by: California Sullivan
---
This class is useful on its own and can be used to create configuration
recipes.
Signed-off-by: California Sullivan
---
...stemd-boot.bbclass => systemd-boot-cfg.bbclass} | 57 --
meta/classes/systemd-boot.bbclass | 70
On 2/27/18 12:19 PM, Juro Bystricky wrote:
The result of running dbus-test-ptest was a series of
various segfaults, interpreted as FAILs. This was a direct consequence
of the test suite loading the installed shared library libdbus-1.so, not the
one built along the test suite.
While we
Upgrade systemd-boot to 236.
As systemd has dropped autotools support, fix configure and compile
failures related to meson.
Signed-off-by: Chen Qi
---
meta/recipes-core/systemd/systemd-boot_234.bb | 43 ---
meta/recipes-core/systemd/systemd-boot_236.bb
Remove the 'fstack-protector' and 'fstack-protector-strong' flags
as a workaround to fix the following error when building for qemux86
and qemuppc with musl.
undefined reference to `__stack_chk_fail_local'
Signed-off-by: Chen Qi
---
The special string "*" on the left hand side of the dependency
specification matches all recipes except the one on the right hand side.
Signed-off-by: Joshua Watt
---
meta/lib/oe/sstatesig.py | 4
1 file changed, 4 insertions(+)
diff --git a/meta/lib/oe/sstatesig.py
Wildcard support in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS allows the native
tools that were in a hardcoded list to be specified in layer.conf with
the other exclusions.
Joshua Watt (3):
sstatesig: Add recipe wildcard
ref-manual: Update documentation for SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
sstatesig:
Now that SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS supports the wildcard syntax,
these exclusions no longer need to be hardcoded
Signed-off-by: Joshua Watt
---
meta/conf/layer.conf | 5 +
meta/lib/oe/sstatesig.py | 5 -
2 files changed, 5 insertions(+), 5 deletions(-)
Changing ICECC_ENV_VERSION or select variables that the user can set to
control the behavior of icecc should not cause recipes to rebuild
Signed-off-by: Joshua Watt
---
meta/classes/icecc.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
Changes to the icecc-create-env recipe should not cause all recipes to
rebuild just because the have inherited icecc.
Signed-off-by: Joshua Watt
---
meta/lib/oe/sstatesig.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oe/sstatesig.py
== Series Details ==
Series: "icecc.bbclass: Ignore more ice..." and 1 more (rev5)
Revision: 5
URL : https://patchwork.openembedded.org/series/11106/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests
== Series Details ==
Series: "icecc.bbclass: Ignore more ice..." and 1 more (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/11106/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests
GLES 2 application cannot use gl3.h header files, remove including gl3.h
when OpenGLESv2 is enabled in webkitgtk
Signed-off-by: Bhargava Sreekantappa Gayathri
Signed-off-by: Manjukumar Matha
---
77 matches
Mail list logo