Fixes build with -fno-common
Signed-off-by: Khem Raj
---
...0001-kexec-Fix-build-with-fno-common.patch | 39 +++
1 file changed, 32 insertions(+), 7 deletions(-)
diff --git
a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-Fix-build-with-fno-common.patch
b/meta/recipes-kerne
This sed expression implements the needed patch to fix compilation with
-fno-common, hopefully this patch will get included in 2.14 release and
we can remove this operation
Signed-off-by: Khem Raj
---
meta/lib/oeqa/runtime/cases/buildcpio.py | 3 ++-
meta/lib/oeqa/sdk/cases/buildcpio.py | 1
Recipe upgrade statistics:
* Succeeded: 38
libubootenv, 0.3, Stefano Babic
iproute2, 5.8.0, Changhyeok Bae
systemd-boot, 246.1, Chen Qi
util-linux, 2.36, Chen Qi
bison, 3.7.1, Chen Qi
build-compare, 2020.05.29-new-commits-available, Paul Egg
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sqlite3* to *3.33.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-sqlite3-upgrade-3.32.3-3.33.0.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libcheck* to *0.15.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libcheck-upgrade-0.15.0-0.15.2.patch
- check the changes to upstream patches and summarize th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libinput* to *1.16.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libinput-upgrade-1.16.0-1.16.1.patch
- check the changes to upstream patches and summarize th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xev* to *1.2.4* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe xev failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitb
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libx11* to *1.6.11* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libx11-upgrade-1.6.9-1.6.11.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *boost* to *1.74.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe boost failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gpgme* to *1.14.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gpgme failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *font-alias* to *1.0.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-font-alias-upgrade-1.0.3-1.0.4.patch
- check the changes to upstream patches and summarize t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *weston* to *8.0.92* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-weston-upgrade-8.0.0-8.0.92.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wpebackend-fdo* to *1.7.1*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-wpebackend-fdo-upgrade-1.6.1-1.7.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20200721*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20200619-20200721.patch
- check the changes to upstream patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-demos* to
*e6956acfbdaf082f930e9cc6bb2c337695d9cebb* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-demos -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpsl* to *0.21.1* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libpsl -V 0.21.1
NOTE: Starting bitbake server...
NOTE: R
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *156* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-153-156.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rsync* to *3.2.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-rsync-upgrade-3.2.2-3.2.3.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-headers* to
*1.2.148.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-vulkan-headers-upgrade-1.2.135.0-1.2.148.0.patch
- check the changes to upstream pa
= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "i686-poky-linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "3.1+snapshot-20200815"
TUNE_FEATURES= &
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpipeline* to *1.5.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libpipeline-upgrade-1.5.2-1.5.3.patch
- check the changes to upstream patches and summarize
47.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.1+snapshot-20200815"
TUNE_FEATURE
Configuration:
BB_VERSION = "1.47.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *build-compare* to
*d95eb3576a73164f3e6e7492ac01c00136239d71* has Succeeded.
Next steps:
- apply the patch: git am
0001-build-compare-upgrade-to-latest-revision.patch
- chec
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gcc-source-10.1.0* to
*10.2.0* has Failed(other errors).
Detailed error information:
The following git command failed: log --pretty=format:"%H" -1 master
fatal: ambiguous argument
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bison* to *3.7.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bison-upgrade-3.6.4-3.7.1.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.15* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: finish -f go
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/re
ild Configuration:
BB_VERSION = "1.47.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "i686-poky-linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSIO
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.15* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: finish -f go-runtime
/home/pokybuild/yocto-worker/auh/build/bu
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-numpy* to *1.19.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-numpy-upgrade-1.19.0-1.19.1.patch
- check the changes to upstream patches and su
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *246.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-systemd-boot-upgrade-246-246.1.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *iproute2* to *5.8.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-iproute2-upgrade-5.7.0-5.8.0.patch
- check the changes to upstream patches and summarize them
figuration:
BB_VERSION = "1.47.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VER
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.1+snapshot-20200815&q
Bruce,
We need
https://github.com/torvalds/linux/commit/168200b6d6ea0cb5765943ec5da5b8149701f36a
backported to 5.4 kernels for perf to build with -fno-common can you
queue this in your kernel updates as soon as you can ?
Thanks
-Khem
On Sat, Aug 15, 2020 at 6:56 PM Khem Raj wrote:
>
> On Sat,
On Sat, Aug 15, 2020 at 3:10 PM Richard Purdie
wrote:
>
> On Tue, 2020-08-04 at 23:17 -0700, Khem Raj wrote:
> > here is a recent build with clang11 which also switched to using
> > -fno-common and errors are pretty much same you will see with gcc10
> > with this patch to revert the -fcommon defau
On Tue, 2020-08-04 at 23:17 -0700, Khem Raj wrote:
> here is a recent build with clang11 which also switched to using
> -fno-common and errors are pretty much same you will see with gcc10
> with this patch to revert the -fcommon defaults.
>
> https://errors.yoctoproject.org/Errors/Build/107234/?li
On Fri, Dec 06, 2019 at 12:00:54PM +, Ross Burton wrote:
>...
> Personally I'm leaning towards keeping zstd out of core *for now* but I
> struggle to have a strong opinion either way.
>...
Is there a chance the "for now" is over?
zstd is becoming more and more popular on the target side,
and
* Drop backported CVE fixes
* Drop cpu backtrace patch from 2015 for debugging an issue which we no longer
see
(patch throws rejects, files have moved)
* Update mips patch to account for file renames
* Update chardev patch to match upstream code changes
* Update webkitgtk patch, qemumips build w
On Fri, Aug 14, 2020 at 11:44:17PM +0200, Alexander Kanavin wrote:
> This needs to go to master first probably?
Better for master might be moving zstd from meta-openembedded,
and then DEPENDS on zstd-native?
IMHO moving target zstd to OE-core is already overdue,
so this would not be solely for cm
40 matches
Mail list logo
