State of OE World, 2019-03-16

State of OE World, 2019-03-16

[Khem Raj]

http://www.openembedded.org/wiki/Bitbake_World_Status

== Failed tasks 2019-03-16 ==

INFO: jenkins-job.sh-1.8.45 Complete log available at
http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log

=== common (2) ===
    * sources/meta-openembedded/meta-networking/recipes-support/drbd/drbd_9.0.16-1.bb:do_compile
    * sources/meta-openembedded/meta-oe/recipes-extended/sysdig/sysdig_git.bb:do_compile

=== common-x86 (1) ===
    * sources/meta-openembedded/meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers_5.2.22.bb:do_compile

=== qemuarm (6) ===
    * sources/meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bb:do_compile
    * sources/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb:do_install
    * sources/meta-openembedded/meta-oe/recipes-support/espeak/espeak_1.48.04.bb:do_compile
    * sources/meta-rust/recipes-devtools/rust/rust_1.33.0.bb:do_compile
    * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
    * sources/openembedded-core/meta/recipes-multimedia/mpeg2dec/mpeg2dec_0.5.1.bb:do_package_qa

=== qemuarm64 (5) ===
    * sources/meta-openembedded/meta-oe/recipes-dbs/mongodb/mongodb_git.bb:do_compile
    * sources/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb:do_compile
    * sources/openembedded-core/meta/recipes-devtools/glide/glide_0.13.2.bb:do_package_qa
    * sources/openembedded-core/meta/recipes-devtools/go/go-dep_0.5.0.bb:do_package_qa
    * sources/openembedded-core/meta/recipes-extended/go-examples/go-helloworld_0.1.bb:do_package_qa

=== qemux86 (4) ===
    * sources/meta-browser/recipes-browser/chromium/chromium-ozone-wayland_72.0.3626.121.bb:do_compile
    * sources/meta-browser/recipes-browser/chromium/chromium-x11_72.0.3626.121.bb:do_compile
    * sources/meta-qt5/recipes-qt/qt5/qt5-creator_git.bb:do_compile
    * sources/meta-rust/recipes-devtools/rust/libstd-rs_1.33.0.bb:do_compile

=== qemux86_64 (1) ===
    * sources/openembedded-core/meta/recipes-core/glibc/glibc-locale_2.29.bb:do_package_qa

=== Number of failed tasks (33) ===
{| class=wikitable
|-
|| qemuarm || 8 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190316_182729.log/
||
|-
|| qemuarm64 || 9 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm64.20190316_204957.log/
||
|-
|| qemux86 || 8 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemux86.20190316_043014.log/
||
|-
|| qemux86_64 || 8 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemux86-64.20190316_070310.log/
||
|}

=== PNBLACKLISTs (2) ===

=== QA issues (61) ===
{| class=wikitable
!| Count ||Issue
|-
||0 ||already-stripped
|-
||0 ||compile-host-path
|-
||0 ||file-rdeps
|-
||0 ||installed-vs-shipped
|-
||0 ||invalid-pkgconfig
|-
||0 ||ldflags
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||qa_pseudo
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||1 ||host-user-contaminated
|-
||1 ||textrel
|-
||3 ||build-deps
|-
||56 ||version-going-backwards
|}



=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===

Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.signatures.20190316_221024.log/


    * ERROR: Nothing RPROVIDES 'bigbuckbunny-1080p' (but
/home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
RDEPENDS on or otherwise requires it)
    * ERROR: Required build target 'meta-world-pkgdata' has no
buildable providers.
    * ERROR: no sigdata files were generated for MACHINE qemux86copy
in /home/jenkins/oe/world/yoe/build/tmpfs/stamps
    * ERROR: Nothing RPROVIDES 'bigbuckbunny-1080p' (but
/home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
RDEPENDS on or otherwise requires it)
    * ERROR: Required build target 'meta-world-pkgdata' has no
buildable providers.
    * ERROR: no sigdata files were generated for MACHINE qemux86 in
/home/jenkins/oe/world/yoe/build/tmpfs/stamps
    * ERROR: Nothing RPROVIDES 'bigbuckbunny-480p' (but
/home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
RDEPENDS on or otherwise requires it)
    * ERROR: Required build target 'meta-world-pkgdata' has no
buildable providers.
    * ERROR: no sigdata files were generated for MACHINE qemuarm in
/home/jenkins/oe/world/yoe/build/tmpfs/stamps


PNBLACKLISTs:
sources/meta-96boards:
sources/meta-atmel:
sources/meta-browser:
sources/meta-freescale:
sources/meta-freescale-3rdparty:
sources/meta-intel:
sources/meta-odroid:
sources/meta-openembedded:
meta-oe/recipes-devtools/librcf/librcf_2.2.0.0.bb:PNBLACKLIST[librcf]
= " error: invalid use of incomplete type 'RCF::AsioIoService {aka
class boost::asio::io_service}; among others?"
sources/meta-qcom:
sources/meta-qt5:
sources/meta-raspberrypi:
sources/meta-riscv:
sources/meta-rust:
sources/meta-ti:
sources/meta-variscite-fslc:
sources/meta-yoe:
sources/openembedded-core:
meta/lib/oeqa/selftest/cases/imagefeatures.py:PNBLACKLIST[busybox] =
"Don't build this"
PNBLACKLIST[android-system] = "depends on lxc from
meta-virtualiazation which isn't included in my world builds"
PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[tearsofsteel-1080p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[build-appliance-image] = "tries to include whole downloads
directory in /home/builder/poky :/"
PNBLACKLIST[smartrefrigerator] = "Needs porting to QT > 5.6"
PNBLACKLIST[qmlbrowser] = "Needs porting to QT > 5.6"
PNBLACKLIST[minehunt] = "Needs porting to QT > 5.6"
PNBLACKLIST[homeautomation] = "Needs porting to QT > 5.6"
PNBLACKLIST[samegame] = "Needs porting to QT > 5.6"
PNBLACKLIST[applicationlauncher] = "Needs porting to QT > 5.6"


QA issues by type:
count: 0 issue: already-stripped


count: 0 issue: libdir


count: 1 issue: textrel
mpeg2dec-0.5.1: ELF binary
'/tmp/work/armv7vet2hf-neon-yoe-linux-gnueabi/mpeg2dec/0.5.1-r0/packages-split/libmpeg2/usr/lib/libmpeg2.so.0.1.0'
has relocations in .text [textrel]


count: 3 issue: build-deps
glide-0.13.2: glide rdepends on libstd-rs, but it isn't a build
dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
[build-deps]
go-dep-0.5.0: go-dep rdepends on libstd-rs, but it isn't a build
dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
[build-deps]
go-helloworld-0.1: go-helloworld rdepends on libstd-rs, but it isn't a
build dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
[build-deps]


count: 0 issue: file-rdeps


count: 56 issue: version-going-backwards
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-dbg went backwards which would break package feeds
from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-dbg went backwards which would break package feeds
from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-dev went backwards which would break package feeds
from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-dev went backwards which would break package feeds
from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-doc went backwards which would break package feeds
from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-doc went backwards which would break package feeds
from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-locale went backwards which would break package
feeds from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-locale went backwards which would break package
feeds from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-src went backwards which would break package feeds
from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-src went backwards which would break package feeds
from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-staticdev went backwards which would break package
feeds from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package
atmel-qt-demo-init-staticdev went backwards which would break package
feeds from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package atmel-qt-demo-init
went backwards which would break package feeds from (0:1.1-r2.79 to
0:1.1-r2.78) [version-going-backwards]
atmel-qt-demo-init-1.1: Package version for package atmel-qt-demo-init
went backwards which would break package feeds from (0:1.1-r2.88 to
0:1.1-r2.87) [version-going-backwards]
os-release-1.0: Package version for package os-release-dbg went
backwards which would break package feeds from (0:1.0-r0.98 to
0:1.0-r0.97) [version-going-backwards]
os-release-1.0: Package version for package os-release-dev went
backwards which would break package feeds from (0:1.0-r0.98 to
0:1.0-r0.97) [version-going-backwards]
os-release-1.0: Package version for package os-release-doc went
backwards which would break package feeds from (0:1.0-r0.98 to
0:1.0-r0.97) [version-going-backwards]
os-release-1.0: Package version for package os-release-locale went
backwards which would break package feeds from (0:1.0-r0.98 to
0:1.0-r0.97) [version-going-backwards]
os-release-1.0: Package version for package os-release-src went
backwards which would break package feeds from (0:1.0-r0.98 to
0:1.0-r0.97) [version-going-backwards]
os-release-1.0: Package version for package os-release-staticdev went
backwards which would break package feeds from (0:1.0-r0.98 to
0:1.0-r0.97) [version-going-backwards]
os-release-1.0: Package version for package os-release went backwards
which would break package feeds from (0:1.0-r0.98 to 0:1.0-r0.97)
[version-going-backwards]
packagegroup-core-standalone-sdk-target-1.0: Package version for
package packagegroup-core-standalone-sdk-target-dbg went backwards
which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
[version-going-backwards]
packagegroup-core-standalone-sdk-target-1.0: Package version for
package packagegroup-core-standalone-sdk-target-dev went backwards
which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
[version-going-backwards]
packagegroup-core-standalone-sdk-target-1.0: Package version for
package packagegroup-core-standalone-sdk-target-ptest went backwards
which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
[version-going-backwards]
packagegroup-core-standalone-sdk-target-1.0: Package version for
package packagegroup-core-standalone-sdk-target-src went backwards
which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
[version-going-backwards]
packagegroup-core-standalone-sdk-target-1.0: Package version for
package packagegroup-core-standalone-sdk-target went backwards which
would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
[version-going-backwards]
packagegroup-core-tools-debug-1.0: Package version for package
packagegroup-core-tools-debug-dbg went backwards which would break
package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
[version-going-backwards]
packagegroup-core-tools-debug-1.0: Package version for package
packagegroup-core-tools-debug-dev went backwards which would break
package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
[version-going-backwards]
packagegroup-core-tools-debug-1.0: Package version for package
packagegroup-core-tools-debug-ptest went backwards which would break
package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
[version-going-backwards]
packagegroup-core-tools-debug-1.0: Package version for package
packagegroup-core-tools-debug-src went backwards which would break
package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
[version-going-backwards]
packagegroup-core-tools-debug-1.0: Package version for package
packagegroup-core-tools-debug went backwards which would break package
feeds from (0:1.0-r3.148 to 0:1.0-r3.147) [version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-dbg went backwards which would break package
feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-debug-dbg went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-debug-dev went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-debug-ptest went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-debug went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-dev went backwards which would break package
feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-extended-dbg went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-extended-dev went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-extended-ptest went backwards which would
break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-extended went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-graphics-dbg went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-graphics-dev went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-graphics-ptest went backwards which would
break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-graphics went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-host-tools-dbg went backwards which would
break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-host-tools-dev went backwards which would
break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-host-tools-ptest went backwards which would
break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-host-tools went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-ptest went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-sdk-dbg went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-sdk-dev went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-sdk-ptest went backwards which would break
package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
[version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-sdk went backwards which would break package
feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted-src went backwards which would break package
feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
packagegroup-self-hosted-1.0: Package version for package
packagegroup-self-hosted went backwards which would break package
feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]


count: 1 issue: host-user-contaminated
glibc-locale-2.29: glibc-locale:
/glibc-binary-localedata-mag-in/usr/lib/locale/mag_IN/LC_CTYPE is
owned by uid 3004, which is the same as the user running bitbake. This
may be due to host contamination [host-user-contaminated]


count: 0 issue: installed-vs-shipped


count: 0 issue: unknown-configure-option


count: 0 issue: symlink-to-sysroot


count: 0 issue: invalid-pkgconfig


count: 0 issue: pkgname


count: 0 issue: ldflags


count: 0 issue: compile-host-path


count: 0 issue: qa_pseudo



This git log matches with the metadata as seen by qemuarm build.
In some cases qemux86 and qemux86-64 builds are built with slightly
different metadata, you can see the exact version near the top of each
log.world.qemu* files linked from the report
~/oe/world/yoe ~/oe/world/yoe

== Tested changes (not included in master yet) - bitbake ==
latest upstream commit:
6065540c .gitattributes: Add to improve git diff for minified css/js files
not included in master yet:

== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit:
afea472cdc systemd: do not disable SELinux with musl
not included in master yet:
55ed568c2d lttng-tools ptest: add missing dependencies
991f971050 lttng-tools ptest: fix test_ust-dl
e0f9710025 lttng-ust: add python3-agent feature
a450f34cd6 resulttool/report: Enable roll-up report for a commit
55f7d0de90 xev: update to 1.2.3
5b2d9d12ec glibc: fix do_populate_sdk fail when multilib used
8c7fbd3b17 mdadm: fix gcc8 maybe-uninitialized/format-overflow warning
432192e0c7 inetutils: Remove talk / talkd from ALTERNATIVES
ac7ea9011b inetutils: Handle rsh, etc more consistently
584c12c892 inetutils: Disable rsh, etc in the build
a2d8bd2705 virglrenderer: requires distro feature opengl
5c0b937f30 glib-2.0: clean up EXTRA_OEMESON
8a47f45962 systemd: drop unused kill-path option
f4b08a0610 shadow: drop inappropriate patch
6a78430c82 class/sanity: strip the output of get_filesystem_id()
95164cbc13 gst-examples: switch to gitlab url and https protocol
5c5c4c80fe systemd: fix CVE-2019-6454
fbded47018 iproute2: add tc to the alternatives list
42741dc701 fixup
3337aa2ced oeqa/manual/bsp-hw.json: test id updated and obsolete test
cases removed
567c6c82b7 oeqa/manual/compliance-test.json: test id updated and
missing test cases added
3bdae69c94 oeqa/manual/kernel-dev.json: test id updated
79da19b826 fixup
57476421be recipes: Add runit and related recipes
db750cc7d3 oeqa: Recognise svlogd as another logger
66ff9aa6d4 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
a47d60761d arch-armv5-dsp.inc: Check for dsp only to enable 'e' in
package arches
a9d66477ee cross-canadian.bbclass: Do not override LIBCOVERRIDE with
SDK libc override
81d34140d4 go: Minor 1.21.1 patch update
4833bdeb9d lttng: Enable on musl and riscv
e633820dc3 packagegroup-core-tools-profile: Do not remove lttng-ust
for musl and risc-v
a32f61aeed gdb: Do not disable lttng-ust on risc-v

== Tested changes (not included in master yet) - meta-openembedded ==
latest upstream commit:
0248b3ee2 wireshark: upgrade to 3.0.0
not included in master yet:
38eb4e77b gvfs/libgtop: inherit upstream-version-is-even
b42de097d squid: upgrade 3.5.27 -> 3.5.28
f7f06219f crash: Upgrade to 7.2.5
b3eeaf449 krb5: Upgrade to 1.17
666c23a48 librelp: Upgrade to 1.4.0
0597e7980 python-pyflame: Disable for risv architecture
9d8943fd2 klibc: Upgrade to 2.0.6 release
059aa8962 netkit-rsh: don't build under musl
02f050205 hdf5: fix installed-vs-shipped QA WARNING
93c5f4704 dnsmasq: avoid conflict with systemd-resolved
3189c0dc8 opencv: fix installed-vs-shipped QA WARNING
60f872278 kexec-tools,kexec: Fix build with latest klibc
e51545e4c mariadb: fix atomic support on arm
b9d6d28cd nghttp2: update to 1.37
d3bfe0a62 libsodium: update to 1.0.17
4464399e5 python-networkmanager: update to 2.1
41c263bf8 mbedtls: update to 2.16.0
98461f1c2 klibc.bbclass: Add libc-klibc to overrides
319789e47 postgresql: Fix build for RISC-V
5c2c565e1 live555: Upgrade to 20190306 release
010c2f388 gstreamer-0.10: Remove recipes
6b77b1a95 libnice: Drop support for gstreamer-0.10
409fb4baa xfce4-mixer: Remove recipe
5ea50a047 packagegroup-meta-multimedia: Remove gst 0.10 related packages
1f0a2ec48 sysdig: Upgrade to 0.24.2+

== Tested changes (not included in master yet) - meta-qt5 ==
latest upstream commit:
77ed8fb qtbase: Adjust target mkspec settings
not included in master yet:
6280bef qtscript: add fix for build with gcc 8.3
e117b58 qtbase: Fix test builds with clang/x86_64
92c34de qt5: cleanup mkspecs
fe88b99 nativesdk-qtbase: use rpath for nativesdk Qt tools
87f0462 qttools/cmake: use OE_QMAKE_PATH_EXTERNAL_HOST_BINS

== Tested changes (not included in master yet) - meta-browser ==
latest upstream commit:
f2b9a4b chromium: Fix chromium build with musl again
not included in master yet:
~/oe/world/yoe

Re: State of OE World, 2019-03-16

[akuster808]

On 3/17/19 8:26 AM, Khem Raj wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Failed tasks 2019-03-16 ==
>
> INFO: jenkins-job.sh-1.8.45 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
>
> === common (2) ===
>     * sources/meta-openembedded/meta-networking/recipes-support/drbd/drbd_9.0.16-1.bb:do_compile
>     * sources/meta-openembedded/meta-oe/recipes-extended/sysdig/sysdig_git.bb:do_compile
>
> === common-x86 (1) ===
>     * sources/meta-openembedded/meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers_5.2.22.bb:do_compile
>
> === qemuarm (6) ===
>     * sources/meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bb:do_compile
>     * sources/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb:do_install
>     * sources/meta-openembedded/meta-oe/recipes-support/espeak/espeak_1.48.04.bb:do_compile
>     * sources/meta-rust/recipes-devtools/rust/rust_1.33.0.bb:do_compile
>     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
>     * sources/openembedded-core/meta/recipes-multimedia/mpeg2dec/mpeg2dec_0.5.1.bb:do_package_qa
>
> === qemuarm64 (5) ===
>     * sources/meta-openembedded/meta-oe/recipes-dbs/mongodb/mongodb_git.bb:do_compile
>     * sources/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb:do_compile
>     * sources/openembedded-core/meta/recipes-devtools/glide/glide_0.13.2.bb:do_package_qa
>     * sources/openembedded-core/meta/recipes-devtools/go/go-dep_0.5.0.bb:do_package_qa
>     * sources/openembedded-core/meta/recipes-extended/go-examples/go-helloworld_0.1.bb:do_package_qa
>
> === qemux86 (4) ===
>     * sources/meta-browser/recipes-browser/chromium/chromium-ozone-wayland_72.0.3626.121.bb:do_compile
>     * sources/meta-browser/recipes-browser/chromium/chromium-x11_72.0.3626.121.bb:do_compile
>     * sources/meta-qt5/recipes-qt/qt5/qt5-creator_git.bb:do_compile
>     * sources/meta-rust/recipes-devtools/rust/libstd-rs_1.33.0.bb:do_compile
>
> === qemux86_64 (1) ===
>     * sources/openembedded-core/meta/recipes-core/glibc/glibc-locale_2.29.bb:do_package_qa

Are any of the meta-openembedded recipes above earmarked for
blacklisting for warrior?

- armin
>
> === Number of failed tasks (33) ===
> {| class=wikitable
> |-
> || qemuarm || 8 ||
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190316_182729.log/
> ||
> |-
> || qemuarm64 || 9 ||
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm64.20190316_204957.log/
> ||
> |-
> || qemux86 || 8 ||
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemux86.20190316_043014.log/
> ||
> |-
> || qemux86_64 || 8 ||
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemux86-64.20190316_070310.log/
> ||
> |}
>
> === PNBLACKLISTs (2) ===
>
> === QA issues (61) ===
> {| class=wikitable
> !| Count ||Issue
> |-
> ||0 ||already-stripped
> |-
> ||0 ||compile-host-path
> |-
> ||0 ||file-rdeps
> |-
> ||0 ||installed-vs-shipped
> |-
> ||0 ||invalid-pkgconfig
> |-
> ||0 ||ldflags
> |-
> ||0 ||libdir
> |-
> ||0 ||pkgname
> |-
> ||0 ||qa_pseudo
> |-
> ||0 ||symlink-to-sysroot
> |-
> ||0 ||unknown-configure-option
> |-
> ||1 ||host-user-contaminated
> |-
> ||1 ||textrel
> |-
> ||3 ||build-deps
> |-
> ||56 ||version-going-backwards
> |}
>
>
>
> === Incorrect PACKAGE_ARCH or sstate signatures (0) ===
>
> Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.signatures.20190316_221024.log/
>
>
>     * ERROR: Nothing RPROVIDES 'bigbuckbunny-1080p' (but
> /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
> RDEPENDS on or otherwise requires it)
>     * ERROR: Required build target 'meta-world-pkgdata' has no
> buildable providers.
>     * ERROR: no sigdata files were generated for MACHINE qemux86copy
> in /home/jenkins/oe/world/yoe/build/tmpfs/stamps
>     * ERROR: Nothing RPROVIDES 'bigbuckbunny-1080p' (but
> /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
> RDEPENDS on or otherwise requires it)
>     * ERROR: Required build target 'meta-world-pkgdata' has no
> buildable providers.
>     * ERROR: no sigdata files were generated for MACHINE qemux86 in
> /home/jenkins/oe/world/yoe/build/tmpfs/stamps
>     * ERROR: Nothing RPROVIDES 'bigbuckbunny-480p' (but
> /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
> RDEPENDS on or otherwise requires it)
>     * ERROR: Required build target 'meta-world-pkgdata' has no
> buildable providers.
>     * ERROR: no sigdata files were generated for MACHINE qemuarm in
> /home/jenkins/oe/world/yoe/build/tmpfs/stamps
>
>
> PNBLACKLISTs:
> sources/meta-96boards:
> sources/meta-atmel:
> sources/meta-browser:
> sources/meta-freescale:
> sources/meta-freescale-3rdparty:
> sources/meta-intel:
> sources/meta-odroid:
> sources/meta-openembedded:
> meta-oe/recipes-devtools/librcf/librcf_2.2.0.0.bb:PNBLACKLIST[librcf]
> = " error: invalid use of incomplete type 'RCF::AsioIoService {aka
> class boost::asio::io_service}; among others?"
> sources/meta-qcom:
> sources/meta-qt5:
> sources/meta-raspberrypi:
> sources/meta-riscv:
> sources/meta-rust:
> sources/meta-ti:
> sources/meta-variscite-fslc:
> sources/meta-yoe:
> sources/openembedded-core:
> meta/lib/oeqa/selftest/cases/imagefeatures.py:PNBLACKLIST[busybox] =
> "Don't build this"
> PNBLACKLIST[android-system] = "depends on lxc from
> meta-virtualiazation which isn't included in my world builds"
> PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be
> tested so much"
> PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be
> tested so much"
> PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
> tested so much"
> PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
> tested so much"
> PNBLACKLIST[tearsofsteel-1080p] = "big and doesn't really need to be
> tested so much"
> PNBLACKLIST[build-appliance-image] = "tries to include whole downloads
> directory in /home/builder/poky :/"
> PNBLACKLIST[smartrefrigerator] = "Needs porting to QT > 5.6"
> PNBLACKLIST[qmlbrowser] = "Needs porting to QT > 5.6"
> PNBLACKLIST[minehunt] = "Needs porting to QT > 5.6"
> PNBLACKLIST[homeautomation] = "Needs porting to QT > 5.6"
> PNBLACKLIST[samegame] = "Needs porting to QT > 5.6"
> PNBLACKLIST[applicationlauncher] = "Needs porting to QT > 5.6"
>
>
> QA issues by type:
> count: 0 issue: already-stripped
>
>
> count: 0 issue: libdir
>
>
> count: 1 issue: textrel
> mpeg2dec-0.5.1: ELF binary
> '/tmp/work/armv7vet2hf-neon-yoe-linux-gnueabi/mpeg2dec/0.5.1-r0/packages-split/libmpeg2/usr/lib/libmpeg2.so.0.1.0'
> has relocations in .text [textrel]
>
>
> count: 3 issue: build-deps
> glide-0.13.2: glide rdepends on libstd-rs, but it isn't a build
> dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
> [build-deps]
> go-dep-0.5.0: go-dep rdepends on libstd-rs, but it isn't a build
> dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
> [build-deps]
> go-helloworld-0.1: go-helloworld rdepends on libstd-rs, but it isn't a
> build dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
> [build-deps]
>
>
> count: 0 issue: file-rdeps
>
>
> count: 56 issue: version-going-backwards
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-dbg went backwards which would break package feeds
> from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-dbg went backwards which would break package feeds
> from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-dev went backwards which would break package feeds
> from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-dev went backwards which would break package feeds
> from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-doc went backwards which would break package feeds
> from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-doc went backwards which would break package feeds
> from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-locale went backwards which would break package
> feeds from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-locale went backwards which would break package
> feeds from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-src went backwards which would break package feeds
> from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-src went backwards which would break package feeds
> from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-staticdev went backwards which would break package
> feeds from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package
> atmel-qt-demo-init-staticdev went backwards which would break package
> feeds from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package atmel-qt-demo-init
> went backwards which would break package feeds from (0:1.1-r2.79 to
> 0:1.1-r2.78) [version-going-backwards]
> atmel-qt-demo-init-1.1: Package version for package atmel-qt-demo-init
> went backwards which would break package feeds from (0:1.1-r2.88 to
> 0:1.1-r2.87) [version-going-backwards]
> os-release-1.0: Package version for package os-release-dbg went
> backwards which would break package feeds from (0:1.0-r0.98 to
> 0:1.0-r0.97) [version-going-backwards]
> os-release-1.0: Package version for package os-release-dev went
> backwards which would break package feeds from (0:1.0-r0.98 to
> 0:1.0-r0.97) [version-going-backwards]
> os-release-1.0: Package version for package os-release-doc went
> backwards which would break package feeds from (0:1.0-r0.98 to
> 0:1.0-r0.97) [version-going-backwards]
> os-release-1.0: Package version for package os-release-locale went
> backwards which would break package feeds from (0:1.0-r0.98 to
> 0:1.0-r0.97) [version-going-backwards]
> os-release-1.0: Package version for package os-release-src went
> backwards which would break package feeds from (0:1.0-r0.98 to
> 0:1.0-r0.97) [version-going-backwards]
> os-release-1.0: Package version for package os-release-staticdev went
> backwards which would break package feeds from (0:1.0-r0.98 to
> 0:1.0-r0.97) [version-going-backwards]
> os-release-1.0: Package version for package os-release went backwards
> which would break package feeds from (0:1.0-r0.98 to 0:1.0-r0.97)
> [version-going-backwards]
> packagegroup-core-standalone-sdk-target-1.0: Package version for
> package packagegroup-core-standalone-sdk-target-dbg went backwards
> which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> [version-going-backwards]
> packagegroup-core-standalone-sdk-target-1.0: Package version for
> package packagegroup-core-standalone-sdk-target-dev went backwards
> which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> [version-going-backwards]
> packagegroup-core-standalone-sdk-target-1.0: Package version for
> package packagegroup-core-standalone-sdk-target-ptest went backwards
> which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> [version-going-backwards]
> packagegroup-core-standalone-sdk-target-1.0: Package version for
> package packagegroup-core-standalone-sdk-target-src went backwards
> which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> [version-going-backwards]
> packagegroup-core-standalone-sdk-target-1.0: Package version for
> package packagegroup-core-standalone-sdk-target went backwards which
> would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> [version-going-backwards]
> packagegroup-core-tools-debug-1.0: Package version for package
> packagegroup-core-tools-debug-dbg went backwards which would break
> package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> [version-going-backwards]
> packagegroup-core-tools-debug-1.0: Package version for package
> packagegroup-core-tools-debug-dev went backwards which would break
> package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> [version-going-backwards]
> packagegroup-core-tools-debug-1.0: Package version for package
> packagegroup-core-tools-debug-ptest went backwards which would break
> package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> [version-going-backwards]
> packagegroup-core-tools-debug-1.0: Package version for package
> packagegroup-core-tools-debug-src went backwards which would break
> package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> [version-going-backwards]
> packagegroup-core-tools-debug-1.0: Package version for package
> packagegroup-core-tools-debug went backwards which would break package
> feeds from (0:1.0-r3.148 to 0:1.0-r3.147) [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-dbg went backwards which would break package
> feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-debug-dbg went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-debug-dev went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-debug-ptest went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-debug went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-dev went backwards which would break package
> feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-extended-dbg went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-extended-dev went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-extended-ptest went backwards which would
> break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-extended went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-graphics-dbg went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-graphics-dev went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-graphics-ptest went backwards which would
> break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-graphics went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-host-tools-dbg went backwards which would
> break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-host-tools-dev went backwards which would
> break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-host-tools-ptest went backwards which would
> break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-host-tools went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-ptest went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-sdk-dbg went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-sdk-dev went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-sdk-ptest went backwards which would break
> package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-sdk went backwards which would break package
> feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted-src went backwards which would break package
> feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> packagegroup-self-hosted-1.0: Package version for package
> packagegroup-self-hosted went backwards which would break package
> feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
>
>
> count: 1 issue: host-user-contaminated
> glibc-locale-2.29: glibc-locale:
> /glibc-binary-localedata-mag-in/usr/lib/locale/mag_IN/LC_CTYPE is
> owned by uid 3004, which is the same as the user running bitbake. This
> may be due to host contamination [host-user-contaminated]
>
>
> count: 0 issue: installed-vs-shipped
>
>
> count: 0 issue: unknown-configure-option
>
>
> count: 0 issue: symlink-to-sysroot
>
>
> count: 0 issue: invalid-pkgconfig
>
>
> count: 0 issue: pkgname
>
>
> count: 0 issue: ldflags
>
>
> count: 0 issue: compile-host-path
>
>
> count: 0 issue: qa_pseudo
>
>
>
> This git log matches with the metadata as seen by qemuarm build.
> In some cases qemux86 and qemux86-64 builds are built with slightly
> different metadata, you can see the exact version near the top of each
> log.world.qemu* files linked from the report
> ~/oe/world/yoe ~/oe/world/yoe
>
> == Tested changes (not included in master yet) - bitbake ==
> latest upstream commit:
> 6065540c .gitattributes: Add to improve git diff for minified css/js files
> not included in master yet:
>
> == Tested changes (not included in master yet) - openembedded-core ==
> latest upstream commit:
> afea472cdc systemd: do not disable SELinux with musl
> not included in master yet:
> 55ed568c2d lttng-tools ptest: add missing dependencies
> 991f971050 lttng-tools ptest: fix test_ust-dl
> e0f9710025 lttng-ust: add python3-agent feature
> a450f34cd6 resulttool/report: Enable roll-up report for a commit
> 55f7d0de90 xev: update to 1.2.3
> 5b2d9d12ec glibc: fix do_populate_sdk fail when multilib used
> 8c7fbd3b17 mdadm: fix gcc8 maybe-uninitialized/format-overflow warning
> 432192e0c7 inetutils: Remove talk / talkd from ALTERNATIVES
> ac7ea9011b inetutils: Handle rsh, etc more consistently
> 584c12c892 inetutils: Disable rsh, etc in the build
> a2d8bd2705 virglrenderer: requires distro feature opengl
> 5c0b937f30 glib-2.0: clean up EXTRA_OEMESON
> 8a47f45962 systemd: drop unused kill-path option
> f4b08a0610 shadow: drop inappropriate patch
> 6a78430c82 class/sanity: strip the output of get_filesystem_id()
> 95164cbc13 gst-examples: switch to gitlab url and https protocol
> 5c5c4c80fe systemd: fix CVE-2019-6454
> fbded47018 iproute2: add tc to the alternatives list
> 42741dc701 fixup
> 3337aa2ced oeqa/manual/bsp-hw.json: test id updated and obsolete test
> cases removed
> 567c6c82b7 oeqa/manual/compliance-test.json: test id updated and
> missing test cases added
> 3bdae69c94 oeqa/manual/kernel-dev.json: test id updated
> 79da19b826 fixup
> 57476421be recipes: Add runit and related recipes
> db750cc7d3 oeqa: Recognise svlogd as another logger
> 66ff9aa6d4 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> a47d60761d arch-armv5-dsp.inc: Check for dsp only to enable 'e' in
> package arches
> a9d66477ee cross-canadian.bbclass: Do not override LIBCOVERRIDE with
> SDK libc override
> 81d34140d4 go: Minor 1.21.1 patch update
> 4833bdeb9d lttng: Enable on musl and riscv
> e633820dc3 packagegroup-core-tools-profile: Do not remove lttng-ust
> for musl and risc-v
> a32f61aeed gdb: Do not disable lttng-ust on risc-v
>
> == Tested changes (not included in master yet) - meta-openembedded ==
> latest upstream commit:
> 0248b3ee2 wireshark: upgrade to 3.0.0
> not included in master yet:
> 38eb4e77b gvfs/libgtop: inherit upstream-version-is-even
> b42de097d squid: upgrade 3.5.27 -> 3.5.28
> f7f06219f crash: Upgrade to 7.2.5
> b3eeaf449 krb5: Upgrade to 1.17
> 666c23a48 librelp: Upgrade to 1.4.0
> 0597e7980 python-pyflame: Disable for risv architecture
> 9d8943fd2 klibc: Upgrade to 2.0.6 release
> 059aa8962 netkit-rsh: don't build under musl
> 02f050205 hdf5: fix installed-vs-shipped QA WARNING
> 93c5f4704 dnsmasq: avoid conflict with systemd-resolved
> 3189c0dc8 opencv: fix installed-vs-shipped QA WARNING
> 60f872278 kexec-tools,kexec: Fix build with latest klibc
> e51545e4c mariadb: fix atomic support on arm
> b9d6d28cd nghttp2: update to 1.37
> d3bfe0a62 libsodium: update to 1.0.17
> 4464399e5 python-networkmanager: update to 2.1
> 41c263bf8 mbedtls: update to 2.16.0
> 98461f1c2 klibc.bbclass: Add libc-klibc to overrides
> 319789e47 postgresql: Fix build for RISC-V
> 5c2c565e1 live555: Upgrade to 20190306 release
> 010c2f388 gstreamer-0.10: Remove recipes
> 6b77b1a95 libnice: Drop support for gstreamer-0.10
> 409fb4baa xfce4-mixer: Remove recipe
> 5ea50a047 packagegroup-meta-multimedia: Remove gst 0.10 related packages
> 1f0a2ec48 sysdig: Upgrade to 0.24.2+
>
> == Tested changes (not included in master yet) - meta-qt5 ==
> latest upstream commit:
> 77ed8fb qtbase: Adjust target mkspec settings
> not included in master yet:
> 6280bef qtscript: add fix for build with gcc 8.3
> e117b58 qtbase: Fix test builds with clang/x86_64
> 92c34de qt5: cleanup mkspecs
> fe88b99 nativesdk-qtbase: use rpath for nativesdk Qt tools
> 87f0462 qttools/cmake: use OE_QMAKE_PATH_EXTERNAL_HOST_BINS
>
> == Tested changes (not included in master yet) - meta-browser ==
> latest upstream commit:
> f2b9a4b chromium: Fix chromium build with musl again
> not included in master yet:
> ~/oe/world/yoe

Re: State of OE World, 2019-03-16

[Khem Raj]

On Sun, Mar 17, 2019 at 9:46 AM akuster808 <akuster808@gmail.com> wrote:
>
>
>
> On 3/17/19 8:26 AM, Khem Raj wrote:
> > http://www.openembedded.org/wiki/Bitbake_World_Status
> >
> > == Failed tasks 2019-03-16 ==
> >
> > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> >
> > === common (2) ===
> >     * sources/meta-openembedded/meta-networking/recipes-support/drbd/drbd_9.0.16-1.bb:do_compile
> >     * sources/meta-openembedded/meta-oe/recipes-extended/sysdig/sysdig_git.bb:do_compile
> >
> > === common-x86 (1) ===
> >     * sources/meta-openembedded/meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers_5.2.22.bb:do_compile
> >
> > === qemuarm (6) ===
> >     * sources/meta-openembedded/meta-oe/recipes-kernel/bpftool/bpftool.bb:do_compile
> >     * sources/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb:do_install
> >     * sources/meta-openembedded/meta-oe/recipes-support/espeak/espeak_1.48.04.bb:do_compile
> >     * sources/meta-rust/recipes-devtools/rust/rust_1.33.0.bb:do_compile
> >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> >     * sources/openembedded-core/meta/recipes-multimedia/mpeg2dec/mpeg2dec_0.5.1.bb:do_package_qa
> >
> > === qemuarm64 (5) ===
> >     * sources/meta-openembedded/meta-oe/recipes-dbs/mongodb/mongodb_git.bb:do_compile
> >     * sources/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest.bb:do_compile
> >     * sources/openembedded-core/meta/recipes-devtools/glide/glide_0.13.2.bb:do_package_qa
> >     * sources/openembedded-core/meta/recipes-devtools/go/go-dep_0.5.0.bb:do_package_qa
> >     * sources/openembedded-core/meta/recipes-extended/go-examples/go-helloworld_0.1.bb:do_package_qa
> >
> > === qemux86 (4) ===
> >     * sources/meta-browser/recipes-browser/chromium/chromium-ozone-wayland_72.0.3626.121.bb:do_compile
> >     * sources/meta-browser/recipes-browser/chromium/chromium-x11_72.0.3626.121.bb:do_compile
> >     * sources/meta-qt5/recipes-qt/qt5/qt5-creator_git.bb:do_compile
> >     * sources/meta-rust/recipes-devtools/rust/libstd-rs_1.33.0.bb:do_compile
> >
> > === qemux86_64 (1) ===
> >     * sources/openembedded-core/meta/recipes-core/glibc/glibc-locale_2.29.bb:do_package_qa
>
> Are any of the meta-openembedded recipes above earmarked for
> blacklisting for warrior?
>

Not yet, I am hoping they will be fixed in due course.

> - armin
> >
> > === Number of failed tasks (33) ===
> > {| class=wikitable
> > |-
> > || qemuarm || 8 ||
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190316_182729.log/
> > ||
> > |-
> > || qemuarm64 || 9 ||
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm64.20190316_204957.log/
> > ||
> > |-
> > || qemux86 || 8 ||
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemux86.20190316_043014.log/
> > ||
> > |-
> > || qemux86_64 || 8 ||
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemux86-64.20190316_070310.log/
> > ||
> > |}
> >
> > === PNBLACKLISTs (2) ===
> >
> > === QA issues (61) ===
> > {| class=wikitable
> > !| Count ||Issue
> > |-
> > ||0 ||already-stripped
> > |-
> > ||0 ||compile-host-path
> > |-
> > ||0 ||file-rdeps
> > |-
> > ||0 ||installed-vs-shipped
> > |-
> > ||0 ||invalid-pkgconfig
> > |-
> > ||0 ||ldflags
> > |-
> > ||0 ||libdir
> > |-
> > ||0 ||pkgname
> > |-
> > ||0 ||qa_pseudo
> > |-
> > ||0 ||symlink-to-sysroot
> > |-
> > ||0 ||unknown-configure-option
> > |-
> > ||1 ||host-user-contaminated
> > |-
> > ||1 ||textrel
> > |-
> > ||3 ||build-deps
> > |-
> > ||56 ||version-going-backwards
> > |}
> >
> >
> >
> > === Incorrect PACKAGE_ARCH or sstate signatures (0) ===
> >
> > Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.signatures.20190316_221024.log/
> >
> >
> >     * ERROR: Nothing RPROVIDES 'bigbuckbunny-1080p' (but
> > /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
> > RDEPENDS on or otherwise requires it)
> >     * ERROR: Required build target 'meta-world-pkgdata' has no
> > buildable providers.
> >     * ERROR: no sigdata files were generated for MACHINE qemux86copy
> > in /home/jenkins/oe/world/yoe/build/tmpfs/stamps
> >     * ERROR: Nothing RPROVIDES 'bigbuckbunny-1080p' (but
> > /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
> > RDEPENDS on or otherwise requires it)
> >     * ERROR: Required build target 'meta-world-pkgdata' has no
> > buildable providers.
> >     * ERROR: no sigdata files were generated for MACHINE qemux86 in
> > /home/jenkins/oe/world/yoe/build/tmpfs/stamps
> >     * ERROR: Nothing RPROVIDES 'bigbuckbunny-480p' (but
> > /home/jenkins/oe/world/yoe/sources/meta-openembedded/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb
> > RDEPENDS on or otherwise requires it)
> >     * ERROR: Required build target 'meta-world-pkgdata' has no
> > buildable providers.
> >     * ERROR: no sigdata files were generated for MACHINE qemuarm in
> > /home/jenkins/oe/world/yoe/build/tmpfs/stamps
> >
> >
> > PNBLACKLISTs:
> > sources/meta-96boards:
> > sources/meta-atmel:
> > sources/meta-browser:
> > sources/meta-freescale:
> > sources/meta-freescale-3rdparty:
> > sources/meta-intel:
> > sources/meta-odroid:
> > sources/meta-openembedded:
> > meta-oe/recipes-devtools/librcf/librcf_2.2.0.0.bb:PNBLACKLIST[librcf]
> > = " error: invalid use of incomplete type 'RCF::AsioIoService {aka
> > class boost::asio::io_service}; among others?"
> > sources/meta-qcom:
> > sources/meta-qt5:
> > sources/meta-raspberrypi:
> > sources/meta-riscv:
> > sources/meta-rust:
> > sources/meta-ti:
> > sources/meta-variscite-fslc:
> > sources/meta-yoe:
> > sources/openembedded-core:
> > meta/lib/oeqa/selftest/cases/imagefeatures.py:PNBLACKLIST[busybox] =
> > "Don't build this"
> > PNBLACKLIST[android-system] = "depends on lxc from
> > meta-virtualiazation which isn't included in my world builds"
> > PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be
> > tested so much"
> > PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be
> > tested so much"
> > PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
> > tested so much"
> > PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
> > tested so much"
> > PNBLACKLIST[tearsofsteel-1080p] = "big and doesn't really need to be
> > tested so much"
> > PNBLACKLIST[build-appliance-image] = "tries to include whole downloads
> > directory in /home/builder/poky :/"
> > PNBLACKLIST[smartrefrigerator] = "Needs porting to QT > 5.6"
> > PNBLACKLIST[qmlbrowser] = "Needs porting to QT > 5.6"
> > PNBLACKLIST[minehunt] = "Needs porting to QT > 5.6"
> > PNBLACKLIST[homeautomation] = "Needs porting to QT > 5.6"
> > PNBLACKLIST[samegame] = "Needs porting to QT > 5.6"
> > PNBLACKLIST[applicationlauncher] = "Needs porting to QT > 5.6"
> >
> >
> > QA issues by type:
> > count: 0 issue: already-stripped
> >
> >
> > count: 0 issue: libdir
> >
> >
> > count: 1 issue: textrel
> > mpeg2dec-0.5.1: ELF binary
> > '/tmp/work/armv7vet2hf-neon-yoe-linux-gnueabi/mpeg2dec/0.5.1-r0/packages-split/libmpeg2/usr/lib/libmpeg2.so.0.1.0'
> > has relocations in .text [textrel]
> >
> >
> > count: 3 issue: build-deps
> > glide-0.13.2: glide rdepends on libstd-rs, but it isn't a build
> > dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
> > [build-deps]
> > go-dep-0.5.0: go-dep rdepends on libstd-rs, but it isn't a build
> > dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
> > [build-deps]
> > go-helloworld-0.1: go-helloworld rdepends on libstd-rs, but it isn't a
> > build dependency, missing libstd-rs in DEPENDS or PACKAGECONFIG?
> > [build-deps]
> >
> >
> > count: 0 issue: file-rdeps
> >
> >
> > count: 56 issue: version-going-backwards
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-dbg went backwards which would break package feeds
> > from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-dbg went backwards which would break package feeds
> > from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-dev went backwards which would break package feeds
> > from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-dev went backwards which would break package feeds
> > from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-doc went backwards which would break package feeds
> > from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-doc went backwards which would break package feeds
> > from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-locale went backwards which would break package
> > feeds from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-locale went backwards which would break package
> > feeds from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-src went backwards which would break package feeds
> > from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-src went backwards which would break package feeds
> > from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-staticdev went backwards which would break package
> > feeds from (0:1.1-r2.79 to 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package
> > atmel-qt-demo-init-staticdev went backwards which would break package
> > feeds from (0:1.1-r2.88 to 0:1.1-r2.87) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package atmel-qt-demo-init
> > went backwards which would break package feeds from (0:1.1-r2.79 to
> > 0:1.1-r2.78) [version-going-backwards]
> > atmel-qt-demo-init-1.1: Package version for package atmel-qt-demo-init
> > went backwards which would break package feeds from (0:1.1-r2.88 to
> > 0:1.1-r2.87) [version-going-backwards]
> > os-release-1.0: Package version for package os-release-dbg went
> > backwards which would break package feeds from (0:1.0-r0.98 to
> > 0:1.0-r0.97) [version-going-backwards]
> > os-release-1.0: Package version for package os-release-dev went
> > backwards which would break package feeds from (0:1.0-r0.98 to
> > 0:1.0-r0.97) [version-going-backwards]
> > os-release-1.0: Package version for package os-release-doc went
> > backwards which would break package feeds from (0:1.0-r0.98 to
> > 0:1.0-r0.97) [version-going-backwards]
> > os-release-1.0: Package version for package os-release-locale went
> > backwards which would break package feeds from (0:1.0-r0.98 to
> > 0:1.0-r0.97) [version-going-backwards]
> > os-release-1.0: Package version for package os-release-src went
> > backwards which would break package feeds from (0:1.0-r0.98 to
> > 0:1.0-r0.97) [version-going-backwards]
> > os-release-1.0: Package version for package os-release-staticdev went
> > backwards which would break package feeds from (0:1.0-r0.98 to
> > 0:1.0-r0.97) [version-going-backwards]
> > os-release-1.0: Package version for package os-release went backwards
> > which would break package feeds from (0:1.0-r0.98 to 0:1.0-r0.97)
> > [version-going-backwards]
> > packagegroup-core-standalone-sdk-target-1.0: Package version for
> > package packagegroup-core-standalone-sdk-target-dbg went backwards
> > which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> > [version-going-backwards]
> > packagegroup-core-standalone-sdk-target-1.0: Package version for
> > package packagegroup-core-standalone-sdk-target-dev went backwards
> > which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> > [version-going-backwards]
> > packagegroup-core-standalone-sdk-target-1.0: Package version for
> > package packagegroup-core-standalone-sdk-target-ptest went backwards
> > which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> > [version-going-backwards]
> > packagegroup-core-standalone-sdk-target-1.0: Package version for
> > package packagegroup-core-standalone-sdk-target-src went backwards
> > which would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> > [version-going-backwards]
> > packagegroup-core-standalone-sdk-target-1.0: Package version for
> > package packagegroup-core-standalone-sdk-target went backwards which
> > would break package feeds from (0:1.0-r8.148 to 0:1.0-r8.147)
> > [version-going-backwards]
> > packagegroup-core-tools-debug-1.0: Package version for package
> > packagegroup-core-tools-debug-dbg went backwards which would break
> > package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> > [version-going-backwards]
> > packagegroup-core-tools-debug-1.0: Package version for package
> > packagegroup-core-tools-debug-dev went backwards which would break
> > package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> > [version-going-backwards]
> > packagegroup-core-tools-debug-1.0: Package version for package
> > packagegroup-core-tools-debug-ptest went backwards which would break
> > package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> > [version-going-backwards]
> > packagegroup-core-tools-debug-1.0: Package version for package
> > packagegroup-core-tools-debug-src went backwards which would break
> > package feeds from (0:1.0-r3.148 to 0:1.0-r3.147)
> > [version-going-backwards]
> > packagegroup-core-tools-debug-1.0: Package version for package
> > packagegroup-core-tools-debug went backwards which would break package
> > feeds from (0:1.0-r3.148 to 0:1.0-r3.147) [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-dbg went backwards which would break package
> > feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-debug-dbg went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-debug-dev went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-debug-ptest went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-debug went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-dev went backwards which would break package
> > feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-extended-dbg went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-extended-dev went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-extended-ptest went backwards which would
> > break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-extended went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-graphics-dbg went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-graphics-dev went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-graphics-ptest went backwards which would
> > break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-graphics went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-host-tools-dbg went backwards which would
> > break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-host-tools-dev went backwards which would
> > break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-host-tools-ptest went backwards which would
> > break package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-host-tools went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-ptest went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-sdk-dbg went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-sdk-dev went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-sdk-ptest went backwards which would break
> > package feeds from (0:1.0-r13.148 to 0:1.0-r13.147)
> > [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-sdk went backwards which would break package
> > feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted-src went backwards which would break package
> > feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> > packagegroup-self-hosted-1.0: Package version for package
> > packagegroup-self-hosted went backwards which would break package
> > feeds from (0:1.0-r13.148 to 0:1.0-r13.147) [version-going-backwards]
> >
> >
> > count: 1 issue: host-user-contaminated
> > glibc-locale-2.29: glibc-locale:
> > /glibc-binary-localedata-mag-in/usr/lib/locale/mag_IN/LC_CTYPE is
> > owned by uid 3004, which is the same as the user running bitbake. This
> > may be due to host contamination [host-user-contaminated]
> >
> >
> > count: 0 issue: installed-vs-shipped
> >
> >
> > count: 0 issue: unknown-configure-option
> >
> >
> > count: 0 issue: symlink-to-sysroot
> >
> >
> > count: 0 issue: invalid-pkgconfig
> >
> >
> > count: 0 issue: pkgname
> >
> >
> > count: 0 issue: ldflags
> >
> >
> > count: 0 issue: compile-host-path
> >
> >
> > count: 0 issue: qa_pseudo
> >
> >
> >
> > This git log matches with the metadata as seen by qemuarm build.
> > In some cases qemux86 and qemux86-64 builds are built with slightly
> > different metadata, you can see the exact version near the top of each
> > log.world.qemu* files linked from the report
> > ~/oe/world/yoe ~/oe/world/yoe
> >
> > == Tested changes (not included in master yet) - bitbake ==
> > latest upstream commit:
> > 6065540c .gitattributes: Add to improve git diff for minified css/js files
> > not included in master yet:
> >
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit:
> > afea472cdc systemd: do not disable SELinux with musl
> > not included in master yet:
> > 55ed568c2d lttng-tools ptest: add missing dependencies
> > 991f971050 lttng-tools ptest: fix test_ust-dl
> > e0f9710025 lttng-ust: add python3-agent feature
> > a450f34cd6 resulttool/report: Enable roll-up report for a commit
> > 55f7d0de90 xev: update to 1.2.3
> > 5b2d9d12ec glibc: fix do_populate_sdk fail when multilib used
> > 8c7fbd3b17 mdadm: fix gcc8 maybe-uninitialized/format-overflow warning
> > 432192e0c7 inetutils: Remove talk / talkd from ALTERNATIVES
> > ac7ea9011b inetutils: Handle rsh, etc more consistently
> > 584c12c892 inetutils: Disable rsh, etc in the build
> > a2d8bd2705 virglrenderer: requires distro feature opengl
> > 5c0b937f30 glib-2.0: clean up EXTRA_OEMESON
> > 8a47f45962 systemd: drop unused kill-path option
> > f4b08a0610 shadow: drop inappropriate patch
> > 6a78430c82 class/sanity: strip the output of get_filesystem_id()
> > 95164cbc13 gst-examples: switch to gitlab url and https protocol
> > 5c5c4c80fe systemd: fix CVE-2019-6454
> > fbded47018 iproute2: add tc to the alternatives list
> > 42741dc701 fixup
> > 3337aa2ced oeqa/manual/bsp-hw.json: test id updated and obsolete test
> > cases removed
> > 567c6c82b7 oeqa/manual/compliance-test.json: test id updated and
> > missing test cases added
> > 3bdae69c94 oeqa/manual/kernel-dev.json: test id updated
> > 79da19b826 fixup
> > 57476421be recipes: Add runit and related recipes
> > db750cc7d3 oeqa: Recognise svlogd as another logger
> > 66ff9aa6d4 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > a47d60761d arch-armv5-dsp.inc: Check for dsp only to enable 'e' in
> > package arches
> > a9d66477ee cross-canadian.bbclass: Do not override LIBCOVERRIDE with
> > SDK libc override
> > 81d34140d4 go: Minor 1.21.1 patch update
> > 4833bdeb9d lttng: Enable on musl and riscv
> > e633820dc3 packagegroup-core-tools-profile: Do not remove lttng-ust
> > for musl and risc-v
> > a32f61aeed gdb: Do not disable lttng-ust on risc-v
> >
> > == Tested changes (not included in master yet) - meta-openembedded ==
> > latest upstream commit:
> > 0248b3ee2 wireshark: upgrade to 3.0.0
> > not included in master yet:
> > 38eb4e77b gvfs/libgtop: inherit upstream-version-is-even
> > b42de097d squid: upgrade 3.5.27 -> 3.5.28
> > f7f06219f crash: Upgrade to 7.2.5
> > b3eeaf449 krb5: Upgrade to 1.17
> > 666c23a48 librelp: Upgrade to 1.4.0
> > 0597e7980 python-pyflame: Disable for risv architecture
> > 9d8943fd2 klibc: Upgrade to 2.0.6 release
> > 059aa8962 netkit-rsh: don't build under musl
> > 02f050205 hdf5: fix installed-vs-shipped QA WARNING
> > 93c5f4704 dnsmasq: avoid conflict with systemd-resolved
> > 3189c0dc8 opencv: fix installed-vs-shipped QA WARNING
> > 60f872278 kexec-tools,kexec: Fix build with latest klibc
> > e51545e4c mariadb: fix atomic support on arm
> > b9d6d28cd nghttp2: update to 1.37
> > d3bfe0a62 libsodium: update to 1.0.17
> > 4464399e5 python-networkmanager: update to 2.1
> > 41c263bf8 mbedtls: update to 2.16.0
> > 98461f1c2 klibc.bbclass: Add libc-klibc to overrides
> > 319789e47 postgresql: Fix build for RISC-V
> > 5c2c565e1 live555: Upgrade to 20190306 release
> > 010c2f388 gstreamer-0.10: Remove recipes
> > 6b77b1a95 libnice: Drop support for gstreamer-0.10
> > 409fb4baa xfce4-mixer: Remove recipe
> > 5ea50a047 packagegroup-meta-multimedia: Remove gst 0.10 related packages
> > 1f0a2ec48 sysdig: Upgrade to 0.24.2+
> >
> > == Tested changes (not included in master yet) - meta-qt5 ==
> > latest upstream commit:
> > 77ed8fb qtbase: Adjust target mkspec settings
> > not included in master yet:
> > 6280bef qtscript: add fix for build with gcc 8.3
> > e117b58 qtbase: Fix test builds with clang/x86_64
> > 92c34de qt5: cleanup mkspecs
> > fe88b99 nativesdk-qtbase: use rpath for nativesdk Qt tools
> > 87f0462 qttools/cmake: use OE_QMAKE_PATH_EXTERNAL_HOST_BINS
> >
> > == Tested changes (not included in master yet) - meta-browser ==
> > latest upstream commit:
> > f2b9a4b chromium: Fix chromium build with musl again
> > not included in master yet:
> > ~/oe/world/yoe
>

Re: State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]

On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
> 
> == Failed tasks 2019-03-16 ==
> 
> INFO: jenkins-job.sh-1.8.45 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> 
>     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile

I was hit by this one as well on some arm targets.

http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log

shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper

| qemu: uncaught target signal 11 (Segmentation fault) - core dumped
| /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"

The interesting part is that this happens only when glibc is built with gold enabled.

I've put a bit more details in temporary work-around here:
https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743

I'm comparing qemuarm glibc build with bfd and gold to see if there is some
significant difference which might cause this and I plan to flash some small
image on my targets to see if libc is broken in runtime as well or only when
running inside qemu-arm.

Is anyone else seeing this as well?

Regards,

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 6476 bytes --]

On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > http://www.openembedded.org/wiki/Bitbake_World_Status
> > 
> > == Failed tasks 2019-03-16 ==
> > 
> > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > 
> >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> 
> I was hit by this one as well on some arm targets.
> 
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> 
> shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> 
> | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> 
> The interesting part is that this happens only when glibc is built with gold enabled.
> 
> I've put a bit more details in temporary work-around here:
> https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> 
> I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> significant difference which might cause this and I plan to flash some small
> image on my targets to see if libc is broken in runtime as well or only when
> running inside qemu-arm.
> 
> Is anyone else seeing this as well?

Checking older world status on the wiki shows that this issue was
introduced somewhere around christmas

This is last world build before the issue:
http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
...
== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit: 
14c291e1fb gcc-runtime: Add missing libc dependency
not included in master yet: 
7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
ced915026d python-native: fix one do_populate_sysroot warning
aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
a09e2db43a sstate: add support for caching shared workdir tasks
c104a34166 grub2: Fix passing null to printf formats
6f364ff8c4 gnupg: Upgrade to 2.2.12 release
0224fec86b glibc: Upgrade towards 2.29 release
2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
b3ab29bdbb gcc-runtime: Drop building libmpx

and this is the first which reported qemu-arm segfault:
== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit: 
95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
not included in master yet: 
0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
bb3eb6bc41 python-native: fix one do_populate_sysroot warning
08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
b81c8650d0 sstate: add support for caching shared workdir tasks
702be42dc9 glibc: Remove site_config and glibc-initial
fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
8652df3a0d gcc: Drop the -initial versions of the compiler
0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
c64531600d newlib: Move away from gcc-initial dependency
0d5fb4428f libssp: Remove dependency on gcc-initial
7dd8829d3e musl: Move away from gcc-initial dependency
9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
6fc9bb5698 glibc: Enable --with-default-link
d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
6efe313b46 glibc: Upgrade towards 2.29 release
dac5dc5067 grub2: Fix passing null to printf formats
bb36d9dc8c gnupg: Upgrade to 2.2.12 release
81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
6fa05e5ace nfs-utils: Disable format-overflow as Werror
8fab7b23ef musl: Update to latest master
a5641cac42 libxcrypt: Upgrade to 4.4.2
c90ec03d07 gdb: Backport a fix to build with gcc9
1adae92573 valgrind: Fix x86_64 build failure with gcc9
38e9e09104 ffmpeg: Backport patch to fix build with gcc9
4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
5cce276d4a binutils: Upgrade to upcoming 2.32 release

and the changes introduced in oe-core between these are:
docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
085530e8ff i2c-tools: upgrade 4.0 -> 4.1
673c2dcf10 common-licenses: update Libpng license text
099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
0860216a81 icecc: patchelf is needed by icecc-create-env
d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
fa6bae80bc icecc: Trivial simplification
6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
547174fc83 gcc-runtime: Drop building libmpx

It's possible that it's not caused by one of these oe-core changes, but one of the pending
yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
later.

I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 8076 bytes --]

On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > 
> > > == Failed tasks 2019-03-16 ==
> > > 
> > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > 
> > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > 
> > I was hit by this one as well on some arm targets.
> > 
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > 
> > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > 
> > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > 
> > The interesting part is that this happens only when glibc is built with gold enabled.
> > 
> > I've put a bit more details in temporary work-around here:
> > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > 
> > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > significant difference which might cause this and I plan to flash some small
> > image on my targets to see if libc is broken in runtime as well or only when
> > running inside qemu-arm.
> > 
> > Is anyone else seeing this as well?
> 
> Checking older world status on the wiki shows that this issue was
> introduced somewhere around christmas
> 
> This is last world build before the issue:
> http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> ...
> == Tested changes (not included in master yet) - openembedded-core ==
> latest upstream commit: 
> 14c291e1fb gcc-runtime: Add missing libc dependency
> not included in master yet: 
> 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> ced915026d python-native: fix one do_populate_sysroot warning
> aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> a09e2db43a sstate: add support for caching shared workdir tasks
> c104a34166 grub2: Fix passing null to printf formats
> 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> 0224fec86b glibc: Upgrade towards 2.29 release
> 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> b3ab29bdbb gcc-runtime: Drop building libmpx
> 
> and this is the first which reported qemu-arm segfault:
> == Tested changes (not included in master yet) - openembedded-core ==
> latest upstream commit: 
> 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> not included in master yet: 
> 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> b81c8650d0 sstate: add support for caching shared workdir tasks
> 702be42dc9 glibc: Remove site_config and glibc-initial
> fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> 8652df3a0d gcc: Drop the -initial versions of the compiler
> 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> c64531600d newlib: Move away from gcc-initial dependency
> 0d5fb4428f libssp: Remove dependency on gcc-initial
> 7dd8829d3e musl: Move away from gcc-initial dependency
> 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> 6fc9bb5698 glibc: Enable --with-default-link
> d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> 6efe313b46 glibc: Upgrade towards 2.29 release
> dac5dc5067 grub2: Fix passing null to printf formats
> bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> 8fab7b23ef musl: Update to latest master
> a5641cac42 libxcrypt: Upgrade to 4.4.2
> c90ec03d07 gdb: Backport a fix to build with gcc9
> 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> 
> and the changes introduced in oe-core between these are:
> docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> 673c2dcf10 common-licenses: update Libpng license text
> 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> 0860216a81 icecc: patchelf is needed by icecc-create-env
> d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> fa6bae80bc icecc: Trivial simplification
> 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> 547174fc83 gcc-runtime: Drop building libmpx
> 
> It's possible that it's not caused by one of these oe-core changes, but one of the pending
> yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> later.
> 
> I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.

git bisect narrowed it down to these oe-core commits:

da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
fa47e2e654 musl: Move away from gcc-initial dependency
9dc6fcd492 libssp: Remove dependency on gcc-initial
44539118ce newlib: Move away from gcc-initial dependency
122217b421 recipes: Drop virtual/libc-for-gcc
d84971928b gcc: Drop the -initial versions of the compiler
62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
c5df105e75 glibc: Remove site_config and glibc-initial
94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
085530e8ff i2c-tools: upgrade 4.0 -> 4.1

my guess was the very last commit "glibc: Enable --with-default-link",
but unfortunately without this fix I cannot build glibc with gold enabled.

Will compare the glibc build to see is there is something obviously wrong
in the output.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

glibc broken when linked with gold Was: [oe] State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 9854 bytes --]

On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > > 
> > > > == Failed tasks 2019-03-16 ==
> > > > 
> > > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > > 
> > > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > > 
> > > I was hit by this one as well on some arm targets.
> > > 
> > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > > 
> > > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > > 
> > > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > > 
> > > The interesting part is that this happens only when glibc is built with gold enabled.
> > > 
> > > I've put a bit more details in temporary work-around here:
> > > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > > 
> > > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > > significant difference which might cause this and I plan to flash some small
> > > image on my targets to see if libc is broken in runtime as well or only when
> > > running inside qemu-arm.
> > > 
> > > Is anyone else seeing this as well?
> > 
> > Checking older world status on the wiki shows that this issue was
> > introduced somewhere around christmas
> > 
> > This is last world build before the issue:
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> > ...
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit: 
> > 14c291e1fb gcc-runtime: Add missing libc dependency
> > not included in master yet: 
> > 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> > ced915026d python-native: fix one do_populate_sysroot warning
> > aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> > a09e2db43a sstate: add support for caching shared workdir tasks
> > c104a34166 grub2: Fix passing null to printf formats
> > 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> > 0224fec86b glibc: Upgrade towards 2.29 release
> > 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > b3ab29bdbb gcc-runtime: Drop building libmpx
> > 
> > and this is the first which reported qemu-arm segfault:
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit: 
> > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > not included in master yet: 
> > 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> > bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> > 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> > b81c8650d0 sstate: add support for caching shared workdir tasks
> > 702be42dc9 glibc: Remove site_config and glibc-initial
> > fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> > 8652df3a0d gcc: Drop the -initial versions of the compiler
> > 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> > c64531600d newlib: Move away from gcc-initial dependency
> > 0d5fb4428f libssp: Remove dependency on gcc-initial
> > 7dd8829d3e musl: Move away from gcc-initial dependency
> > 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> > e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> > 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> > f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > 6fc9bb5698 glibc: Enable --with-default-link
> > d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > 6efe313b46 glibc: Upgrade towards 2.29 release
> > dac5dc5067 grub2: Fix passing null to printf formats
> > bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> > 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> > 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> > 8fab7b23ef musl: Update to latest master
> > a5641cac42 libxcrypt: Upgrade to 4.4.2
> > c90ec03d07 gdb: Backport a fix to build with gcc9
> > 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> > 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> > 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> > 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> > 
> > and the changes introduced in oe-core between these are:
> > docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > 673c2dcf10 common-licenses: update Libpng license text
> > 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> > 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> > 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> > a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> > 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> > dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> > 0860216a81 icecc: patchelf is needed by icecc-create-env
> > d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> > 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> > fa6bae80bc icecc: Trivial simplification
> > 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> > 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> > 547174fc83 gcc-runtime: Drop building libmpx
> > 
> > It's possible that it's not caused by one of these oe-core changes, but one of the pending
> > yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> > later.
> > 
> > I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.
> 
> git bisect narrowed it down to these oe-core commits:
> 
> da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
> 7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
> 5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
> 5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
> fa47e2e654 musl: Move away from gcc-initial dependency
> 9dc6fcd492 libssp: Remove dependency on gcc-initial
> 44539118ce newlib: Move away from gcc-initial dependency
> 122217b421 recipes: Drop virtual/libc-for-gcc
> d84971928b gcc: Drop the -initial versions of the compiler
> 62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
> c5df105e75 glibc: Remove site_config and glibc-initial
> 94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> 56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
> 95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> 
> my guess was the very last commit "glibc: Enable --with-default-link",
> but unfortunately without this fix I cannot build glibc with gold enabled.
> 
> Will compare the glibc build to see is there is something obviously wrong
> in the output.

I've confirmed that forcing bfd linker in glibc do_compile resolves the
issue with gobject-introspection (image build still running will try to
flash it tomorrow).

The simples work-around in oe-core:
http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=054c72716f0648ff2f0770c1010857596442223e
or as bbappend:
https://github.com/webOS-ports/meta-webos-ports/commit/020d31892780b69fa64a3a6a146283e831ccd2e9
this is what I'm testing with now, notice that setting just LDFLAGS
isn't enough, because LDFLAGS are unset in glibc.do_compile

I don't know if it's worth spending more time trying to get the glibc
working with gold, it looks like:
http://git.openembedded.org/openembedded-core/commit/?id=7bbc453ac2b8d63680855789948a145fc448017f
resolved the linker script issue (I was seeing the same error with
oe-core 5d0307fbef just this fix) reported here:
https://sourceware.org/bugzilla/show_bug.cgi?id=24148

but there are other bugs like:
https://sourceware.org/bugzilla/show_bug.cgi?id=10937
https://sourceware.org/bugzilla/show_bug.cgi?id=18103
e.g. gentoo is also explicitly disabling gold for glibc builds:
https://github.com/gentoo/gentoo/blob/16e1c37bdc84b2ac5df10511f63e478d8e49435e/sys-libs/glibc/glibc-2.29-r1.ebuild#L767

Can someone confirm that glibc built with gold works for him on arm
(I haven't seen this on x86, aarch64)? Or should we just force bfd in
oe-core recipe?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

glibc broken when linked with gold Was: State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 9854 bytes --]

On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > > 
> > > > == Failed tasks 2019-03-16 ==
> > > > 
> > > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > > 
> > > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > > 
> > > I was hit by this one as well on some arm targets.
> > > 
> > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > > 
> > > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > > 
> > > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > > 
> > > The interesting part is that this happens only when glibc is built with gold enabled.
> > > 
> > > I've put a bit more details in temporary work-around here:
> > > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > > 
> > > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > > significant difference which might cause this and I plan to flash some small
> > > image on my targets to see if libc is broken in runtime as well or only when
> > > running inside qemu-arm.
> > > 
> > > Is anyone else seeing this as well?
> > 
> > Checking older world status on the wiki shows that this issue was
> > introduced somewhere around christmas
> > 
> > This is last world build before the issue:
> > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> > ...
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit: 
> > 14c291e1fb gcc-runtime: Add missing libc dependency
> > not included in master yet: 
> > 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> > ced915026d python-native: fix one do_populate_sysroot warning
> > aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> > a09e2db43a sstate: add support for caching shared workdir tasks
> > c104a34166 grub2: Fix passing null to printf formats
> > 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> > 0224fec86b glibc: Upgrade towards 2.29 release
> > 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > b3ab29bdbb gcc-runtime: Drop building libmpx
> > 
> > and this is the first which reported qemu-arm segfault:
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit: 
> > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > not included in master yet: 
> > 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> > bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> > 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> > b81c8650d0 sstate: add support for caching shared workdir tasks
> > 702be42dc9 glibc: Remove site_config and glibc-initial
> > fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> > 8652df3a0d gcc: Drop the -initial versions of the compiler
> > 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> > c64531600d newlib: Move away from gcc-initial dependency
> > 0d5fb4428f libssp: Remove dependency on gcc-initial
> > 7dd8829d3e musl: Move away from gcc-initial dependency
> > 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> > e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> > 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> > f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > 6fc9bb5698 glibc: Enable --with-default-link
> > d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > 6efe313b46 glibc: Upgrade towards 2.29 release
> > dac5dc5067 grub2: Fix passing null to printf formats
> > bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> > 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> > 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> > 8fab7b23ef musl: Update to latest master
> > a5641cac42 libxcrypt: Upgrade to 4.4.2
> > c90ec03d07 gdb: Backport a fix to build with gcc9
> > 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> > 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> > 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> > 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> > 
> > and the changes introduced in oe-core between these are:
> > docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > 673c2dcf10 common-licenses: update Libpng license text
> > 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> > 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> > 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> > a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> > 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> > dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> > 0860216a81 icecc: patchelf is needed by icecc-create-env
> > d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> > 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> > fa6bae80bc icecc: Trivial simplification
> > 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> > 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> > 547174fc83 gcc-runtime: Drop building libmpx
> > 
> > It's possible that it's not caused by one of these oe-core changes, but one of the pending
> > yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> > later.
> > 
> > I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.
> 
> git bisect narrowed it down to these oe-core commits:
> 
> da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
> 7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
> 5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
> 5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
> fa47e2e654 musl: Move away from gcc-initial dependency
> 9dc6fcd492 libssp: Remove dependency on gcc-initial
> 44539118ce newlib: Move away from gcc-initial dependency
> 122217b421 recipes: Drop virtual/libc-for-gcc
> d84971928b gcc: Drop the -initial versions of the compiler
> 62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
> c5df105e75 glibc: Remove site_config and glibc-initial
> 94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> 56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
> 95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> 
> my guess was the very last commit "glibc: Enable --with-default-link",
> but unfortunately without this fix I cannot build glibc with gold enabled.
> 
> Will compare the glibc build to see is there is something obviously wrong
> in the output.

I've confirmed that forcing bfd linker in glibc do_compile resolves the
issue with gobject-introspection (image build still running will try to
flash it tomorrow).

The simples work-around in oe-core:
http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=054c72716f0648ff2f0770c1010857596442223e
or as bbappend:
https://github.com/webOS-ports/meta-webos-ports/commit/020d31892780b69fa64a3a6a146283e831ccd2e9
this is what I'm testing with now, notice that setting just LDFLAGS
isn't enough, because LDFLAGS are unset in glibc.do_compile

I don't know if it's worth spending more time trying to get the glibc
working with gold, it looks like:
http://git.openembedded.org/openembedded-core/commit/?id=7bbc453ac2b8d63680855789948a145fc448017f
resolved the linker script issue (I was seeing the same error with
oe-core 5d0307fbef just this fix) reported here:
https://sourceware.org/bugzilla/show_bug.cgi?id=24148

but there are other bugs like:
https://sourceware.org/bugzilla/show_bug.cgi?id=10937
https://sourceware.org/bugzilla/show_bug.cgi?id=18103
e.g. gentoo is also explicitly disabling gold for glibc builds:
https://github.com/gentoo/gentoo/blob/16e1c37bdc84b2ac5df10511f63e478d8e49435e/sys-libs/glibc/glibc-2.29-r1.ebuild#L767

Can someone confirm that glibc built with gold works for him on arm
(I haven't seen this on x86, aarch64)? Or should we just force bfd in
oe-core recipe?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: glibc broken when linked with gold Was: [oe] State of OE World, 2019-03-16

[Khem Raj]

On Wed, Mar 27, 2019 at 3:32 PM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> > On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > > >
> > > > > == Failed tasks 2019-03-16 ==
> > > > >
> > > > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > > >
> > > > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > > >
> > > > I was hit by this one as well on some arm targets.
> > > >
> > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > > >
> > > > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > > >
> > > > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > > > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > > >
> > > > The interesting part is that this happens only when glibc is built with gold enabled.
> > > >
> > > > I've put a bit more details in temporary work-around here:
> > > > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > > >
> > > > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > > > significant difference which might cause this and I plan to flash some small
> > > > image on my targets to see if libc is broken in runtime as well or only when
> > > > running inside qemu-arm.
> > > >
> > > > Is anyone else seeing this as well?
> > >
> > > Checking older world status on the wiki shows that this issue was
> > > introduced somewhere around christmas
> > >
> > > This is last world build before the issue:
> > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> > > ...
> > > == Tested changes (not included in master yet) - openembedded-core ==
> > > latest upstream commit:
> > > 14c291e1fb gcc-runtime: Add missing libc dependency
> > > not included in master yet:
> > > 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> > > ced915026d python-native: fix one do_populate_sysroot warning
> > > aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> > > a09e2db43a sstate: add support for caching shared workdir tasks
> > > c104a34166 grub2: Fix passing null to printf formats
> > > 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> > > 0224fec86b glibc: Upgrade towards 2.29 release
> > > 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > b3ab29bdbb gcc-runtime: Drop building libmpx
> > >
> > > and this is the first which reported qemu-arm segfault:
> > > == Tested changes (not included in master yet) - openembedded-core ==
> > > latest upstream commit:
> > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > not included in master yet:
> > > 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> > > bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> > > 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> > > b81c8650d0 sstate: add support for caching shared workdir tasks
> > > 702be42dc9 glibc: Remove site_config and glibc-initial
> > > fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> > > 8652df3a0d gcc: Drop the -initial versions of the compiler
> > > 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> > > c64531600d newlib: Move away from gcc-initial dependency
> > > 0d5fb4428f libssp: Remove dependency on gcc-initial
> > > 7dd8829d3e musl: Move away from gcc-initial dependency
> > > 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> > > e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> > > 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> > > f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > > 6fc9bb5698 glibc: Enable --with-default-link
> > > d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > 6efe313b46 glibc: Upgrade towards 2.29 release
> > > dac5dc5067 grub2: Fix passing null to printf formats
> > > bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> > > 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> > > 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> > > 8fab7b23ef musl: Update to latest master
> > > a5641cac42 libxcrypt: Upgrade to 4.4.2
> > > c90ec03d07 gdb: Backport a fix to build with gcc9
> > > 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> > > 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> > > 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> > > 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> > >
> > > and the changes introduced in oe-core between these are:
> > > docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > > 673c2dcf10 common-licenses: update Libpng license text
> > > 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> > > 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> > > 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> > > a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> > > 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> > > dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> > > 0860216a81 icecc: patchelf is needed by icecc-create-env
> > > d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> > > 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> > > fa6bae80bc icecc: Trivial simplification
> > > 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> > > 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> > > 547174fc83 gcc-runtime: Drop building libmpx
> > >
> > > It's possible that it's not caused by one of these oe-core changes, but one of the pending
> > > yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> > > later.
> > >
> > > I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.
> >
> > git bisect narrowed it down to these oe-core commits:
> >
> > da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
> > 7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
> > 5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
> > 5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
> > fa47e2e654 musl: Move away from gcc-initial dependency
> > 9dc6fcd492 libssp: Remove dependency on gcc-initial
> > 44539118ce newlib: Move away from gcc-initial dependency
> > 122217b421 recipes: Drop virtual/libc-for-gcc
> > d84971928b gcc: Drop the -initial versions of the compiler
> > 62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
> > c5df105e75 glibc: Remove site_config and glibc-initial
> > 94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > 56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
> > 95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> >
> > my guess was the very last commit "glibc: Enable --with-default-link",
> > but unfortunately without this fix I cannot build glibc with gold enabled.
> >
> > Will compare the glibc build to see is there is something obviously wrong
> > in the output.
>
> I've confirmed that forcing bfd linker in glibc do_compile resolves the
> issue with gobject-introspection (image build still running will try to
> flash it tomorrow).
>
> The simples work-around in oe-core:
> http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=054c72716f0648ff2f0770c1010857596442223e
> or as bbappend:
> https://github.com/webOS-ports/meta-webos-ports/commit/020d31892780b69fa64a3a6a146283e831ccd2e9
> this is what I'm testing with now, notice that setting just LDFLAGS
> isn't enough, because LDFLAGS are unset in glibc.do_compile
>
> I don't know if it's worth spending more time trying to get the glibc
> working with gold, it looks like:

i agree, your change to force bfd linker is acceptable approach
please propose it to OE-Core directly.


> http://git.openembedded.org/openembedded-core/commit/?id=7bbc453ac2b8d63680855789948a145fc448017f
> resolved the linker script issue (I was seeing the same error with
> oe-core 5d0307fbef just this fix) reported here:
> https://sourceware.org/bugzilla/show_bug.cgi?id=24148
>
> but there are other bugs like:
> https://sourceware.org/bugzilla/show_bug.cgi?id=10937
> https://sourceware.org/bugzilla/show_bug.cgi?id=18103
> e.g. gentoo is also explicitly disabling gold for glibc builds:
> https://github.com/gentoo/gentoo/blob/16e1c37bdc84b2ac5df10511f63e478d8e49435e/sys-libs/glibc/glibc-2.29-r1.ebuild#L767
>
> Can someone confirm that glibc built with gold works for him on arm
> (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> oe-core recipe?
>
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: glibc broken when linked with gold Was: State of OE World, 2019-03-16

[Khem Raj]

On Wed, Mar 27, 2019 at 3:32 PM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> > On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > > >
> > > > > == Failed tasks 2019-03-16 ==
> > > > >
> > > > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > > >
> > > > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > > >
> > > > I was hit by this one as well on some arm targets.
> > > >
> > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > > >
> > > > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > > >
> > > > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > > > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > > >
> > > > The interesting part is that this happens only when glibc is built with gold enabled.
> > > >
> > > > I've put a bit more details in temporary work-around here:
> > > > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > > >
> > > > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > > > significant difference which might cause this and I plan to flash some small
> > > > image on my targets to see if libc is broken in runtime as well or only when
> > > > running inside qemu-arm.
> > > >
> > > > Is anyone else seeing this as well?
> > >
> > > Checking older world status on the wiki shows that this issue was
> > > introduced somewhere around christmas
> > >
> > > This is last world build before the issue:
> > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> > > ...
> > > == Tested changes (not included in master yet) - openembedded-core ==
> > > latest upstream commit:
> > > 14c291e1fb gcc-runtime: Add missing libc dependency
> > > not included in master yet:
> > > 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> > > ced915026d python-native: fix one do_populate_sysroot warning
> > > aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> > > a09e2db43a sstate: add support for caching shared workdir tasks
> > > c104a34166 grub2: Fix passing null to printf formats
> > > 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> > > 0224fec86b glibc: Upgrade towards 2.29 release
> > > 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > b3ab29bdbb gcc-runtime: Drop building libmpx
> > >
> > > and this is the first which reported qemu-arm segfault:
> > > == Tested changes (not included in master yet) - openembedded-core ==
> > > latest upstream commit:
> > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > not included in master yet:
> > > 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> > > bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> > > 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> > > b81c8650d0 sstate: add support for caching shared workdir tasks
> > > 702be42dc9 glibc: Remove site_config and glibc-initial
> > > fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> > > 8652df3a0d gcc: Drop the -initial versions of the compiler
> > > 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> > > c64531600d newlib: Move away from gcc-initial dependency
> > > 0d5fb4428f libssp: Remove dependency on gcc-initial
> > > 7dd8829d3e musl: Move away from gcc-initial dependency
> > > 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> > > e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> > > 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> > > f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > > 6fc9bb5698 glibc: Enable --with-default-link
> > > d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > 6efe313b46 glibc: Upgrade towards 2.29 release
> > > dac5dc5067 grub2: Fix passing null to printf formats
> > > bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> > > 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> > > 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> > > 8fab7b23ef musl: Update to latest master
> > > a5641cac42 libxcrypt: Upgrade to 4.4.2
> > > c90ec03d07 gdb: Backport a fix to build with gcc9
> > > 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> > > 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> > > 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> > > 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> > >
> > > and the changes introduced in oe-core between these are:
> > > docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > > 673c2dcf10 common-licenses: update Libpng license text
> > > 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> > > 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> > > 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> > > a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> > > 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> > > dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> > > 0860216a81 icecc: patchelf is needed by icecc-create-env
> > > d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> > > 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> > > fa6bae80bc icecc: Trivial simplification
> > > 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> > > 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> > > 547174fc83 gcc-runtime: Drop building libmpx
> > >
> > > It's possible that it's not caused by one of these oe-core changes, but one of the pending
> > > yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> > > later.
> > >
> > > I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.
> >
> > git bisect narrowed it down to these oe-core commits:
> >
> > da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
> > 7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
> > 5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
> > 5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
> > fa47e2e654 musl: Move away from gcc-initial dependency
> > 9dc6fcd492 libssp: Remove dependency on gcc-initial
> > 44539118ce newlib: Move away from gcc-initial dependency
> > 122217b421 recipes: Drop virtual/libc-for-gcc
> > d84971928b gcc: Drop the -initial versions of the compiler
> > 62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
> > c5df105e75 glibc: Remove site_config and glibc-initial
> > 94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > 56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
> > 95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> >
> > my guess was the very last commit "glibc: Enable --with-default-link",
> > but unfortunately without this fix I cannot build glibc with gold enabled.
> >
> > Will compare the glibc build to see is there is something obviously wrong
> > in the output.
>
> I've confirmed that forcing bfd linker in glibc do_compile resolves the
> issue with gobject-introspection (image build still running will try to
> flash it tomorrow).
>
> The simples work-around in oe-core:
> http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=054c72716f0648ff2f0770c1010857596442223e
> or as bbappend:
> https://github.com/webOS-ports/meta-webos-ports/commit/020d31892780b69fa64a3a6a146283e831ccd2e9
> this is what I'm testing with now, notice that setting just LDFLAGS
> isn't enough, because LDFLAGS are unset in glibc.do_compile
>
> I don't know if it's worth spending more time trying to get the glibc
> working with gold, it looks like:

i agree, your change to force bfd linker is acceptable approach
please propose it to OE-Core directly.


> http://git.openembedded.org/openembedded-core/commit/?id=7bbc453ac2b8d63680855789948a145fc448017f
> resolved the linker script issue (I was seeing the same error with
> oe-core 5d0307fbef just this fix) reported here:
> https://sourceware.org/bugzilla/show_bug.cgi?id=24148
>
> but there are other bugs like:
> https://sourceware.org/bugzilla/show_bug.cgi?id=10937
> https://sourceware.org/bugzilla/show_bug.cgi?id=18103
> e.g. gentoo is also explicitly disabling gold for glibc builds:
> https://github.com/gentoo/gentoo/blob/16e1c37bdc84b2ac5df10511f63e478d8e49435e/sys-libs/glibc/glibc-2.29-r1.ebuild#L767
>
> Can someone confirm that glibc built with gold works for him on arm
> (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> oe-core recipe?
>
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: glibc broken when linked with gold Was: [oe] State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 11445 bytes --]

On Wed, Mar 27, 2019 at 10:08:32PM -0700, Khem Raj wrote:
> On Wed, Mar 27, 2019 at 3:32 PM Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> > > On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > > > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > > > >
> > > > > > == Failed tasks 2019-03-16 ==
> > > > > >
> > > > > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > > > >
> > > > > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > > > >
> > > > > I was hit by this one as well on some arm targets.
> > > > >
> > > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > > > >
> > > > > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > > > >
> > > > > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > > > > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > > > >
> > > > > The interesting part is that this happens only when glibc is built with gold enabled.
> > > > >
> > > > > I've put a bit more details in temporary work-around here:
> > > > > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > > > >
> > > > > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > > > > significant difference which might cause this and I plan to flash some small
> > > > > image on my targets to see if libc is broken in runtime as well or only when
> > > > > running inside qemu-arm.
> > > > >
> > > > > Is anyone else seeing this as well?
> > > >
> > > > Checking older world status on the wiki shows that this issue was
> > > > introduced somewhere around christmas
> > > >
> > > > This is last world build before the issue:
> > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> > > > ...
> > > > == Tested changes (not included in master yet) - openembedded-core ==
> > > > latest upstream commit:
> > > > 14c291e1fb gcc-runtime: Add missing libc dependency
> > > > not included in master yet:
> > > > 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> > > > ced915026d python-native: fix one do_populate_sysroot warning
> > > > aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> > > > a09e2db43a sstate: add support for caching shared workdir tasks
> > > > c104a34166 grub2: Fix passing null to printf formats
> > > > 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> > > > 0224fec86b glibc: Upgrade towards 2.29 release
> > > > 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > > b3ab29bdbb gcc-runtime: Drop building libmpx
> > > >
> > > > and this is the first which reported qemu-arm segfault:
> > > > == Tested changes (not included in master yet) - openembedded-core ==
> > > > latest upstream commit:
> > > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > > not included in master yet:
> > > > 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> > > > bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> > > > 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> > > > b81c8650d0 sstate: add support for caching shared workdir tasks
> > > > 702be42dc9 glibc: Remove site_config and glibc-initial
> > > > fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> > > > 8652df3a0d gcc: Drop the -initial versions of the compiler
> > > > 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> > > > c64531600d newlib: Move away from gcc-initial dependency
> > > > 0d5fb4428f libssp: Remove dependency on gcc-initial
> > > > 7dd8829d3e musl: Move away from gcc-initial dependency
> > > > 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> > > > e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> > > > 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> > > > f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > > > 6fc9bb5698 glibc: Enable --with-default-link
> > > > d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > > 6efe313b46 glibc: Upgrade towards 2.29 release
> > > > dac5dc5067 grub2: Fix passing null to printf formats
> > > > bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> > > > 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> > > > 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> > > > 8fab7b23ef musl: Update to latest master
> > > > a5641cac42 libxcrypt: Upgrade to 4.4.2
> > > > c90ec03d07 gdb: Backport a fix to build with gcc9
> > > > 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> > > > 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> > > > 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> > > > 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> > > >
> > > > and the changes introduced in oe-core between these are:
> > > > docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> > > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > > > 673c2dcf10 common-licenses: update Libpng license text
> > > > 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> > > > 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> > > > 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> > > > a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> > > > 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> > > > dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> > > > 0860216a81 icecc: patchelf is needed by icecc-create-env
> > > > d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> > > > 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> > > > fa6bae80bc icecc: Trivial simplification
> > > > 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> > > > 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> > > > 547174fc83 gcc-runtime: Drop building libmpx
> > > >
> > > > It's possible that it's not caused by one of these oe-core changes, but one of the pending
> > > > yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> > > > later.
> > > >
> > > > I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.
> > >
> > > git bisect narrowed it down to these oe-core commits:
> > >
> > > da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
> > > 7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
> > > 5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
> > > 5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
> > > fa47e2e654 musl: Move away from gcc-initial dependency
> > > 9dc6fcd492 libssp: Remove dependency on gcc-initial
> > > 44539118ce newlib: Move away from gcc-initial dependency
> > > 122217b421 recipes: Drop virtual/libc-for-gcc
> > > d84971928b gcc: Drop the -initial versions of the compiler
> > > 62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
> > > c5df105e75 glibc: Remove site_config and glibc-initial
> > > 94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > > 56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
> > > 95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > >
> > > my guess was the very last commit "glibc: Enable --with-default-link",
> > > but unfortunately without this fix I cannot build glibc with gold enabled.
> > >
> > > Will compare the glibc build to see is there is something obviously wrong
> > > in the output.
> >
> > I've confirmed that forcing bfd linker in glibc do_compile resolves the
> > issue with gobject-introspection (image build still running will try to
> > flash it tomorrow).
> >
> > The simples work-around in oe-core:
> > http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=054c72716f0648ff2f0770c1010857596442223e
> > or as bbappend:
> > https://github.com/webOS-ports/meta-webos-ports/commit/020d31892780b69fa64a3a6a146283e831ccd2e9

If you need to use this, then add "export" as well which is needed
because of the "unset" in the main recipe (wasn't needed when I had both
these changes included in the build at first).
https://github.com/webOS-ports/meta-webos-ports/commit/0e737ad167a14591e73ca3fa47d31108038ec3e2

> > this is what I'm testing with now, notice that setting just LDFLAGS
> > isn't enough, because LDFLAGS are unset in glibc.do_compile
> >
> > I don't know if it's worth spending more time trying to get the glibc
> > working with gold, it looks like:
> 
> i agree, your change to force bfd linker is acceptable approach
> please propose it to OE-Core directly.

Send for oe-core:
https://patchwork.openembedded.org/patch/159874/
but more information might be needed before it gets applied to oe-core
as discussed with RP. I'll try to get serial cable working on my Nexus 5
to test it there in runtime, but maybe someone could beat me to it with
some more easily hackable 32bit arm board.

> 
> > http://git.openembedded.org/openembedded-core/commit/?id=7bbc453ac2b8d63680855789948a145fc448017f
> > resolved the linker script issue (I was seeing the same error with
> > oe-core 5d0307fbef just this fix) reported here:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=24148
> >
> > but there are other bugs like:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=10937
> > https://sourceware.org/bugzilla/show_bug.cgi?id=18103
> > e.g. gentoo is also explicitly disabling gold for glibc builds:
> > https://github.com/gentoo/gentoo/blob/16e1c37bdc84b2ac5df10511f63e478d8e49435e/sys-libs/glibc/glibc-2.29-r1.ebuild#L767
> >
> > Can someone confirm that glibc built with gold works for him on arm
> > (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> > oe-core recipe?
> >
> > --
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: glibc broken when linked with gold Was: State of OE World, 2019-03-16

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 11445 bytes --]

On Wed, Mar 27, 2019 at 10:08:32PM -0700, Khem Raj wrote:
> On Wed, Mar 27, 2019 at 3:32 PM Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> > > On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > > > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > > > http://www.openembedded.org/wiki/Bitbake_World_Status
> > > > > >
> > > > > > == Failed tasks 2019-03-16 ==
> > > > > >
> > > > > > INFO: jenkins-job.sh-1.8.45 Complete log available at
> > > > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20190317_082308.log
> > > > > >
> > > > > >     * sources/openembedded-core/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile
> > > > >
> > > > > I was hit by this one as well on some arm targets.
> > > > >
> > > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.world.qemuarm.20190321_215508.log/bitbake.log
> > > > >
> > > > > shows that it's actually from qemu-arm segfault inside g-ir-scanner-qemuwrapper
> > > > >
> > > > > | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> > > > > | /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper: line 6:  1959 Segmentation fault      (core dumped) PSEUDO_UNLOAD=1 qemu-arm -r 3.2.0 -L /home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot -E LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//usr/lib:/home/jenkins/oe/world/yoe/build/tmpfs/work/armv7vet2hf-neon-yoe-linux-gnueabi/gobject-introspection/1.58.3-r0/recipe-sysroot//lib "$@"
> > > > >
> > > > > The interesting part is that this happens only when glibc is built with gold enabled.
> > > > >
> > > > > I've put a bit more details in temporary work-around here:
> > > > > https://github.com/shr-distribution/meta-smartphone/commit/8f06eb355ead85464b1a1bbaa82584504df15743
> > > > >
> > > > > I'm comparing qemuarm glibc build with bfd and gold to see if there is some
> > > > > significant difference which might cause this and I plan to flash some small
> > > > > image on my targets to see if libc is broken in runtime as well or only when
> > > > > running inside qemu-arm.
> > > > >
> > > > > Is anyone else seeing this as well?
> > > >
> > > > Checking older world status on the wiki shows that this issue was
> > > > introduced somewhere around christmas
> > > >
> > > > This is last world build before the issue:
> > > > http://logs.nslu2-linux.org/buildlogs/oe/world/warrior/log.report.20181219_112425.log
> > > > ...
> > > > == Tested changes (not included in master yet) - openembedded-core ==
> > > > latest upstream commit:
> > > > 14c291e1fb gcc-runtime: Add missing libc dependency
> > > > not included in master yet:
> > > > 7e2ab991fa python/python3: use cc_basename to replace CC for checking compiler
> > > > ced915026d python-native: fix one do_populate_sysroot warning
> > > > aee47f3e82 netbase: add entry to /etc/hosts according to /etc/hostname
> > > > a09e2db43a sstate: add support for caching shared workdir tasks
> > > > c104a34166 grub2: Fix passing null to printf formats
> > > > 6f364ff8c4 gnupg: Upgrade to 2.2.12 release
> > > > 0224fec86b glibc: Upgrade towards 2.29 release
> > > > 2486349782 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > > b3ab29bdbb gcc-runtime: Drop building libmpx
> > > >
> > > > and this is the first which reported qemu-arm segfault:
> > > > == Tested changes (not included in master yet) - openembedded-core ==
> > > > latest upstream commit:
> > > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > > not included in master yet:
> > > > 0c9db0ae7d python/python3: use cc_basename to replace CC for checking compiler
> > > > bb3eb6bc41 python-native: fix one do_populate_sysroot warning
> > > > 08a205f872 netbase: add entry to /etc/hosts according to /etc/hostname
> > > > b81c8650d0 sstate: add support for caching shared workdir tasks
> > > > 702be42dc9 glibc: Remove site_config and glibc-initial
> > > > fc230822d8 gcc: Drop gcc-cross-initial and use gcc-cross instead
> > > > 8652df3a0d gcc: Drop the -initial versions of the compiler
> > > > 0c2f6dfa2f recipes: Drop virtual/libc-for-gcc
> > > > c64531600d newlib: Move away from gcc-initial dependency
> > > > 0d5fb4428f libssp: Remove dependency on gcc-initial
> > > > 7dd8829d3e musl: Move away from gcc-initial dependency
> > > > 9abdb4d6ca tcmode-default: Drop pinnings for gcc-initial based recipes
> > > > e02724e8f8 base.bbclass, classextend.py: Drop catering to gcc-initial
> > > > 7756cb7d17 oeqa/concurrencytest: fix for locating meta-selftest
> > > > f4c68c39e7 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > > > 6fc9bb5698 glibc: Enable --with-default-link
> > > > d4cb282bc6 gcc-9.0: Add recipes for upcoming gcc 9.0 release in mid-2019
> > > > 6efe313b46 glibc: Upgrade towards 2.29 release
> > > > dac5dc5067 grub2: Fix passing null to printf formats
> > > > bb36d9dc8c gnupg: Upgrade to 2.2.12 release
> > > > 81059437a5 gnupg: Do not apply -Woverride-init guard for gcc >= 9
> > > > 6fa05e5ace nfs-utils: Disable format-overflow as Werror
> > > > 8fab7b23ef musl: Update to latest master
> > > > a5641cac42 libxcrypt: Upgrade to 4.4.2
> > > > c90ec03d07 gdb: Backport a fix to build with gcc9
> > > > 1adae92573 valgrind: Fix x86_64 build failure with gcc9
> > > > 38e9e09104 ffmpeg: Backport patch to fix build with gcc9
> > > > 4e1fa57743 binutils: Upgrade to latest on 2.31 release branch
> > > > 5cce276d4a binutils: Upgrade to upcoming 2.32 release
> > > >
> > > > and the changes introduced in oe-core between these are:
> > > > docker-shr @ ~/openembedded-core $ git log --oneline 14c291e1fb..95659bed3f
> > > > 95659bed3f populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > > > 673c2dcf10 common-licenses: update Libpng license text
> > > > 099aecfaa3 libpng: upgrade 1.6.35 -> 1.6.36
> > > > 6574bb7523 harfbuzz: upgrade 2.1.3 -> 2.2.0
> > > > 8286e9d79d sqlite3: upgrade 3.25.3 -> 3.26.0
> > > > a33170ff9a libatomic-ops: upgrade 7.6.6 -> 7.6.8
> > > > 6a10ff0bcd gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1
> > > > dd2c4d9d85 eudev: upgrade 3.2.5 -> 3.2.7
> > > > 0860216a81 icecc: patchelf is needed by icecc-create-env
> > > > d2fcaeb153 icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time
> > > > 4455c46bf7 icecc: Syntax error meant that we weren't waiting for tarball generation
> > > > fa6bae80bc icecc: Trivial simplification
> > > > 6d6788a3ea icecc: readlink -f on the recipe-sysroot gcc/g++
> > > > 1ee90ec89a libxcrypt: Fix nativesdk build with gcc9
> > > > 547174fc83 gcc-runtime: Drop building libmpx
> > > >
> > > > It's possible that it's not caused by one of these oe-core changes, but one of the pending
> > > > yoe changes (like those 2 binutils upgrades) which were merged to oe-core in some form a bit
> > > > later.
> > > >
> > > > I'll verify if the issue is reproducible with oe-core 95659bed3f and continue the bisect from there.
> > >
> > > git bisect narrowed it down to these oe-core commits:
> > >
> > > da527d73f5 oeqa/utils/qemurunner: Print output when failed to login
> > > 7bbc453ac2 (refs/bisect/bad) glibc: Enable --with-default-link
> > > 5d0307fbef (HEAD) base.bbclass, classextend.py: Drop catering to gcc-initial
> > > 5b2fd1c724 tcmode-default: Drop pinnings for gcc-initial based recipes
> > > fa47e2e654 musl: Move away from gcc-initial dependency
> > > 9dc6fcd492 libssp: Remove dependency on gcc-initial
> > > 44539118ce newlib: Move away from gcc-initial dependency
> > > 122217b421 recipes: Drop virtual/libc-for-gcc
> > > d84971928b gcc: Drop the -initial versions of the compiler
> > > 62b7308b8c gcc: Drop gcc-cross-initial and use gcc-cross instead
> > > c5df105e75 glibc: Remove site_config and glibc-initial
> > > 94bece16c2 crosssdk/cross-canadian: Set LIBCOVERRIDE correctly
> > > 56d2493a9a oeqa/concurrencytest: fix for locating meta-selftest
> > > 95659bed3f (glibc-95659bed3f, refs/bisect/good-95659bed3f6f3216b346f70cfc9ffae9788c0fc1) populate_sdk_ext.bbclass: Include site.conf in parsing for contents for local.conf
> > > 085530e8ff i2c-tools: upgrade 4.0 -> 4.1
> > >
> > > my guess was the very last commit "glibc: Enable --with-default-link",
> > > but unfortunately without this fix I cannot build glibc with gold enabled.
> > >
> > > Will compare the glibc build to see is there is something obviously wrong
> > > in the output.
> >
> > I've confirmed that forcing bfd linker in glibc do_compile resolves the
> > issue with gobject-introspection (image build still running will try to
> > flash it tomorrow).
> >
> > The simples work-around in oe-core:
> > http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=054c72716f0648ff2f0770c1010857596442223e
> > or as bbappend:
> > https://github.com/webOS-ports/meta-webos-ports/commit/020d31892780b69fa64a3a6a146283e831ccd2e9

If you need to use this, then add "export" as well which is needed
because of the "unset" in the main recipe (wasn't needed when I had both
these changes included in the build at first).
https://github.com/webOS-ports/meta-webos-ports/commit/0e737ad167a14591e73ca3fa47d31108038ec3e2

> > this is what I'm testing with now, notice that setting just LDFLAGS
> > isn't enough, because LDFLAGS are unset in glibc.do_compile
> >
> > I don't know if it's worth spending more time trying to get the glibc
> > working with gold, it looks like:
> 
> i agree, your change to force bfd linker is acceptable approach
> please propose it to OE-Core directly.

Send for oe-core:
https://patchwork.openembedded.org/patch/159874/
but more information might be needed before it gets applied to oe-core
as discussed with RP. I'll try to get serial cable working on my Nexus 5
to test it there in runtime, but maybe someone could beat me to it with
some more easily hackable 32bit arm board.

> 
> > http://git.openembedded.org/openembedded-core/commit/?id=7bbc453ac2b8d63680855789948a145fc448017f
> > resolved the linker script issue (I was seeing the same error with
> > oe-core 5d0307fbef just this fix) reported here:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=24148
> >
> > but there are other bugs like:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=10937
> > https://sourceware.org/bugzilla/show_bug.cgi?id=18103
> > e.g. gentoo is also explicitly disabling gold for glibc builds:
> > https://github.com/gentoo/gentoo/blob/16e1c37bdc84b2ac5df10511f63e478d8e49435e/sys-libs/glibc/glibc-2.29-r1.ebuild#L767
> >
> > Can someone confirm that glibc built with gold works for him on arm
> > (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> > oe-core recipe?
> >
> > --
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: glibc broken when linked with gold Was: [oe] State of OE World, 2019-03-16

[Trevor Woerner]

On Thu 2019-03-28 @ 03:40:33 PM, Martin Jansa wrote:
> Send for oe-core:
> https://patchwork.openembedded.org/patch/159874/
> but more information might be needed before it gets applied to oe-core
> as discussed with RP. I'll try to get serial cable working on my Nexus 5
> to test it there in runtime, but maybe someone could beat me to it with
> some more easily hackable 32bit arm board.
> 
> > > Can someone confirm that glibc built with gold works for him on arm
> > > (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> > > oe-core recipe?

I have an Olimex imx233-olinuxino-maxi that I build for and test regularly
(arm926ej-s, ARMv5).

Yesterday I performed two builds from master with the following configuration:

	Build Configuration:
	BB_VERSION           = "1.40.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuseleap-15.0"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "imx233-olinuxino-maxi"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv5 thumb dsp"
	TARGET_FPU           = "soft"
	meta-freescale       = "master:08173f472244817b85fe4af8ab2add7a0090b122"
	meta-fsl-arm-extra   = "master:b4d2c8462220e7038adffc0a151767ef8da07c5d"
	meta                 = "master:aeaca9bb1b1c8bf44818945dc4b2cbd6d4b5cef2"
	meta-oe
	meta-python
	meta-networking      = "master:24dd9328f7ec964bbad25b7061366f9f2ff6194d"

Both builds explicitly included gobject-introspection.

The first build was done as-is (i.e. using the bfd linker). The second build
had the following in conf/local.conf:

	DISTRO_FEATURES_append = " ld-is-gold"

The default build succeeded. The gold build failed as expected while running
qemu trying to build gobject-introspection.

The good build boots on the hardware and runs fine (as far as I can tell):

	OpenEmbedded nodistro.0 imx233-olinuxino-maxi ttyAMA0

	imx233-olinuxino-maxi login: root
	root@imx233-olinuxino-maxi:~# uname -a
	Linux imx233-olinuxino-maxi 5.0.3-fslc+g20d8efe36350 #1 Thu Mar 28 17:09:20 UTC 2019 armv5tejl armv5tejl armv5tejl GNU/Linux
	root@imx233-olinuxino-maxi:~# g-ir-compiler --help
	Usage:
	  g-ir-compiler [OPTION?]

	Help Options:
	  -h, --help                    Show help options

	Application Options:
	  --includedir                  include directories in GIR search path
	  -o, --output=FILE             output file
	  -m, --module=NAME             module to compile
	  -l, --shared-library=FILE     shared library
	  --debug                       show debug messages
	  --verbose                     show verbose messages

Re: [OE-core] glibc broken when linked with gold Was: State of OE World, 2019-03-16

[Trevor Woerner]

On Thu 2019-03-28 @ 03:40:33 PM, Martin Jansa wrote:
> Send for oe-core:
> https://patchwork.openembedded.org/patch/159874/
> but more information might be needed before it gets applied to oe-core
> as discussed with RP. I'll try to get serial cable working on my Nexus 5
> to test it there in runtime, but maybe someone could beat me to it with
> some more easily hackable 32bit arm board.
> 
> > > Can someone confirm that glibc built with gold works for him on arm
> > > (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> > > oe-core recipe?

I have an Olimex imx233-olinuxino-maxi that I build for and test regularly
(arm926ej-s, ARMv5).

Yesterday I performed two builds from master with the following configuration:

	Build Configuration:
	BB_VERSION           = "1.40.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuseleap-15.0"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "imx233-olinuxino-maxi"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv5 thumb dsp"
	TARGET_FPU           = "soft"
	meta-freescale       = "master:08173f472244817b85fe4af8ab2add7a0090b122"
	meta-fsl-arm-extra   = "master:b4d2c8462220e7038adffc0a151767ef8da07c5d"
	meta                 = "master:aeaca9bb1b1c8bf44818945dc4b2cbd6d4b5cef2"
	meta-oe
	meta-python
	meta-networking      = "master:24dd9328f7ec964bbad25b7061366f9f2ff6194d"

Both builds explicitly included gobject-introspection.

The first build was done as-is (i.e. using the bfd linker). The second build
had the following in conf/local.conf:

	DISTRO_FEATURES_append = " ld-is-gold"

The default build succeeded. The gold build failed as expected while running
qemu trying to build gobject-introspection.

The good build boots on the hardware and runs fine (as far as I can tell):

	OpenEmbedded nodistro.0 imx233-olinuxino-maxi ttyAMA0

	imx233-olinuxino-maxi login: root
	root@imx233-olinuxino-maxi:~# uname -a
	Linux imx233-olinuxino-maxi 5.0.3-fslc+g20d8efe36350 #1 Thu Mar 28 17:09:20 UTC 2019 armv5tejl armv5tejl armv5tejl GNU/Linux
	root@imx233-olinuxino-maxi:~# g-ir-compiler --help
	Usage:
	  g-ir-compiler [OPTION?]

	Help Options:
	  -h, --help                    Show help options

	Application Options:
	  --includedir                  include directories in GIR search path
	  -o, --output=FILE             output file
	  -m, --module=NAME             module to compile
	  -l, --shared-library=FILE     shared library
	  --debug                       show debug messages
	  --verbose                     show verbose messages

Re: glibc broken when linked with gold Was: [oe] State of OE World, 2019-03-16

[Trevor Woerner]

An image built with gold fails on the hardware.

I was able to build core-image-minimal with gold enabled:

configuration:
	Build Configuration:
	BB_VERSION           = "1.40.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuseleap-15.0"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "imx233-olinuxino-maxi"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv5 thumb dsp"
	TARGET_FPU           = "soft"
	meta-fsl-arm-extra   = "master:b4d2c8462220e7038adffc0a151767ef8da07c5d"
	meta-freescale       = "master:08173f472244817b85fe4af8ab2add7a0090b122"
	meta                 = "master:aeaca9bb1b1c8bf44818945dc4b2cbd6d4b5cef2"

conf/local.conf addition:
	DISTRO_FEATURES_append = " ld-is-gold"

When run, the kernel is unable to run init, and panics:

	[    4.050000] Freeing unused kernel memory: 308K
	[    4.050000] This architecture does not have kernel memory protection.
	[    4.060000] Run /sbin/init as init process
	[    4.120000] hub 1-1:1.0: USB hub found
	[    4.130000] hub 1-1:1.0: 3 ports detected
	[    4.140000] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
	[    4.140000] CPU: 0 PID: 1 Comm: init Not tainted 5.0.3-fslc+g20d8efe36350 #1
	[    4.140000] Hardware name: Freescale MXS (Device Tree)
	[    4.140000] [<c0010df8>] (unwind_backtrace) from [<c000e730>] (show_stack+0x10/0x14)
	[    4.140000] [<c000e730>] (show_stack) from [<c001a9bc>] (panic+0xec/0x2d8)
	[    4.140000] [<c001a9bc>] (panic) from [<c001d3b0>] (do_exit+0xa44/0xaa4)
	[    4.140000] [<c001d3b0>] (do_exit) from [<c001e65c>] (do_group_exit+0x38/0xbc)
	[    4.140000] [<c001e65c>] (do_group_exit) from [<c002a1c0>] (get_signal+0x110/0x98c)
	[    4.140000] [<c002a1c0>] (get_signal) from [<c000dd6c>] (do_work_pending+0x120/0x5fc)
	[    4.140000] [<c000dd6c>] (do_work_pending) from [<c0009034>] (slow_work_pending+0xc/0x20)
	[    4.140000] Exception stack(0xc343dfb0 to 0xc343dff8)
	[    4.140000] dfa0:                                     bebd7f10 484113c4 00000000 48431fd0
	[    4.140000] dfc0: 00000934 00000000 00000000 00000000 00000000 00000000 00021504 bebd7f0c
	[    4.140000] dfe0: 48431fd0 bebd7ed0 48410a40 484113f4 00000010 ffffffff
	[    4.140000] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

Re: [OE-core] glibc broken when linked with gold Was: State of OE World, 2019-03-16

[Trevor Woerner]

An image built with gold fails on the hardware.

I was able to build core-image-minimal with gold enabled:

configuration:
	Build Configuration:
	BB_VERSION           = "1.40.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuseleap-15.0"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "imx233-olinuxino-maxi"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv5 thumb dsp"
	TARGET_FPU           = "soft"
	meta-fsl-arm-extra   = "master:b4d2c8462220e7038adffc0a151767ef8da07c5d"
	meta-freescale       = "master:08173f472244817b85fe4af8ab2add7a0090b122"
	meta                 = "master:aeaca9bb1b1c8bf44818945dc4b2cbd6d4b5cef2"

conf/local.conf addition:
	DISTRO_FEATURES_append = " ld-is-gold"

When run, the kernel is unable to run init, and panics:

	[    4.050000] Freeing unused kernel memory: 308K
	[    4.050000] This architecture does not have kernel memory protection.
	[    4.060000] Run /sbin/init as init process
	[    4.120000] hub 1-1:1.0: USB hub found
	[    4.130000] hub 1-1:1.0: 3 ports detected
	[    4.140000] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
	[    4.140000] CPU: 0 PID: 1 Comm: init Not tainted 5.0.3-fslc+g20d8efe36350 #1
	[    4.140000] Hardware name: Freescale MXS (Device Tree)
	[    4.140000] [<c0010df8>] (unwind_backtrace) from [<c000e730>] (show_stack+0x10/0x14)
	[    4.140000] [<c000e730>] (show_stack) from [<c001a9bc>] (panic+0xec/0x2d8)
	[    4.140000] [<c001a9bc>] (panic) from [<c001d3b0>] (do_exit+0xa44/0xaa4)
	[    4.140000] [<c001d3b0>] (do_exit) from [<c001e65c>] (do_group_exit+0x38/0xbc)
	[    4.140000] [<c001e65c>] (do_group_exit) from [<c002a1c0>] (get_signal+0x110/0x98c)
	[    4.140000] [<c002a1c0>] (get_signal) from [<c000dd6c>] (do_work_pending+0x120/0x5fc)
	[    4.140000] [<c000dd6c>] (do_work_pending) from [<c0009034>] (slow_work_pending+0xc/0x20)
	[    4.140000] Exception stack(0xc343dfb0 to 0xc343dff8)
	[    4.140000] dfa0:                                     bebd7f10 484113c4 00000000 48431fd0
	[    4.140000] dfc0: 00000934 00000000 00000000 00000000 00000000 00000000 00021504 bebd7f0c
	[    4.140000] dfe0: 48431fd0 bebd7ed0 48410a40 484113f4 00000010 ffffffff
	[    4.140000] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---