* State of bitbake world, Failed tasks 2017-03-27
@ 2017-03-29 7:23 Martin Jansa
2017-03-29 8:35 ` [OE-core] " Patrick Ohly
0 siblings, 1 reply; 11+ messages in thread
From: Martin Jansa @ 2017-03-29 7:23 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer, openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 7026 bytes --]
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies !!|Signatures !!colspan='12'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64 ||qemuarm||max||min ||qemux86||max||min ||all ||already-stripped ||libdir ||textrel ||build-deps ||file-rdeps ||version-going-backwards ||host-user-contaminated ||installed-vs-shipped ||unknown-configure-option ||symlink-to-sysroot ||invalid-pkgconfig ||pkgname ||
|-
||2017-03-27 ||15 ||17 ||18 ||N/A ||N/A ||N/A ||N/A ||N/A ||N/A ||0 ||0 ||0 ||3 ||0 ||0 ||0 ||1 ||0 ||0 ||0 ||0 ||0 ||
|}
http://www.openembedded.org/wiki/Bitbake_World_Status
== Failed tasks 2017-03-27 ==
INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
=== common (15) ===
* meta-openembedded/meta-multimedia/recipes-multimedia/alsa-equal/alsa-equal_0.6.bb:do_fetch
* meta-openembedded/meta-oe/recipes-extended/lcdproc/lcdproc_0.5.7.bb:do_compile
* meta-openembedded/meta-oe/recipes-extended/libexecinfo/libexecinfo_1.1.bb:do_compile
* meta-openembedded/meta-oe/recipes-extended/libqb/libqb_0.17.2.bb:do_fetch
* meta-openembedded/meta-oe/recipes-extended/tcsh/tcsh_6.18.01.bb:do_compile
* meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/ttf-abyssinica_1.500.bb:do_fetch
* meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/ttf-liberation-sans-narrow_1.07.4.bb:do_fetch
* meta-openembedded/meta-oe/recipes-support/atop/atop_git.bb:do_fetch
* meta-openembedded/meta-oe/recipes-support/gpm/gpm_git.bb:do_install
* meta-openembedded/meta-oe/recipes-support/hwdata/hwdata_0.291.bb:do_fetch
* meta-openembedded/meta-oe/recipes-support/mailcap/mailcap_2.1.46.bb:do_fetch
* meta-openembedded/meta-oe/recipes-support/opencv/opencv_3.2.bb:do_configure
* meta-openembedded/meta-oe/recipes-support/zile/zile_2.4.11.bb:do_install
* meta-openembedded/meta-python/recipes-devtools/python/python-slip-dbus_0.6.1.bb:do_fetch
* virtual:native:meta-openembedded/meta-efl/recipes-efl/efl/efl_1.15.1.bb:do_compile
=== common-x86 (2) ===
* meta-openembedded/meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers_5.1.14.bb:do_install
* openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
=== qemuarm (0) ===
=== qemux86 (0) ===
=== qemux86_64 (1) ===
* meta-openembedded/meta-oe/recipes-extended/tiptop/tiptop_2.3.bb:do_compile
=== Number of failed tasks (50) ===
{| class=wikitable
|-
|| qemuarm || 15 || http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemuarm.20170325_211949.log/ || http://errors.yoctoproject.org/Errors/Build/34932/
|-
|| qemux86 || 17 || http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemux86.20170325_211955.log/ || http://errors.yoctoproject.org/Errors/Build/34933/
|-
|| qemux86_64 || 18 || http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.world.qemux86-64.20170327_003511.log/ || http://errors.yoctoproject.org/Errors/Build/34986/
|}
=== PNBLACKLISTs (350) ===
=== QA issues (4) ===
{| class=wikitable
!| Count ||Issue
|-
||0 ||already-stripped
|-
||0 ||build-deps
|-
||0 ||file-rdeps
|-
||0 ||installed-vs-shipped
|-
||0 ||invalid-pkgconfig
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||0 ||version-going-backwards
|-
||1 ||host-user-contaminated
|-
||3 ||textrel
|}
=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===
Complete log: http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.signatures.20170326_203903.log/
No issues detected
== Tested changes (not included in master yet) - bitbake ==
latest upstream commit:
751b06c bitbake-diffsigs: Add debug support
not included in master yet:
b2f45ac world-image: add extra target
== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit:
552bd78 wic: use kernel_dir to find systemd-efi bootloader
not included in master yet:
268177c qemux86: Add identical qemux86copy variant for tests
b77bb05 sstate-sysroot-cruft.sh: Extend the whitelist
d4c27b7 recipes: Replace "cp -a" with "cp -R --no-dereference --preserve=mode,links"
a90bb2a buildhistory.bbclass: metadata-revs show repo parent
37e4ad6 metadata-revs: provide more information
82c2609 report-error: Allow to upload reports automatically
886304b Revert "openssl: Fix build with clang"
7524fc7 Revert "mesa: Contain configure search for llvm"
== Tested changes (not included in master yet) - meta-openembedded ==
latest upstream commit:
f2dfae5 curlpp: 0.7.3 -> 0.8.1
not included in master yet:
cd99d41 dnsmasq: disable the service by default
433ed04 gperftools: fix do_compile failure for qemuppc
99d4ea4 nginx: make user in nginx.conf consistent with the default value
3a59904 gpm: Update to use git src uri
a58b5d0 rapidjson: Update to 1.1.0 + git
7358057 libtorrent, rtorrent: Update to latest
97fc925 sgio: Fix missing GNU_HASH errors
50c4c2c libmatroska: Fix missing GNU_HASH errors
effb692 smstools3: Fix GNU_HASH errors
4f1fb1e procmail: Fix GNU_HASH errors, pass LDFLAGS
ba292da gradm: Fix GNU_HASH QA errors
0a41bbd zile: Fix build with musl
b23530b picocom: Upgrade to 2.2
b700371 samsung-soc-utils: Remove -static
e8307ed digitemp: Update past 3.7.1 release
605fb8d memstat: Fix build with musl
db8fd09 libexecinfo: Add recipe
bda7efb lvm2: Avoid an unnecessary dependency on bash
cb96e68 lvm2: libdevicemapper package needs udev rules and dmsetup
74a720c lvm2: fix lvm2-native RRECOMMENDS problem
cf4a857 atop: Fix build with musl
98548d1 gflags: correct S and update library install directory
af20aaa libssh: Force to use gcc toolchain
4b27cca libnice: Upgrade to 0.1.13
dd3f48b lio-utils: Fix GNU_HASH QA errors
4053e7a nginx: set sane defaults for temp directories
499ade1 nginx: make sure the user is correctly set for the volatile directories
8ae141e aufs-utils-native: define CC
5e944ba fwts: upgrade to 17.03.00 release
e009f03 efl: append -fPIC only for target builds
== Tested changes (not included in master yet) - meta-qt5 ==
latest upstream commit:
ff073f0 nativesdk-qtbase: pass -no-icu for deterministic builds
not included in master yet:
== Tested changes (not included in master yet) - meta-browser ==
latest upstream commit:
021a954 chromium-browser: add missing dependency on gperf-native
not included in master yet:
a9dd704 chromium: disable generate_character_data for x86
== Tested changes (not included in master yet) - meta-webos-ports ==
latest upstream commit:
4d4ffcb packagegroup-luneos-extended: drop qtscenegraph-adaptation
not included in master yet:
== Tested changes (not included in master yet) - meta-smartphone ==
latest upstream commit:
e39c265 android-system-image: fix builds that don't have overlay-libs
not included in master yet:
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: State of bitbake world, Failed tasks 2017-03-27
2017-03-29 7:23 State of bitbake world, Failed tasks 2017-03-27 Martin Jansa
@ 2017-03-29 8:35 ` Patrick Ohly
0 siblings, 0 replies; 11+ messages in thread
From: Patrick Ohly @ 2017-03-29 8:35 UTC (permalink / raw)
To: Martin Jansa
Cc: openembedded-devel, Patches and discussions about the oe-core layer
On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
That used OE-core 552bd78, if I read this right:
== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit:
552bd78 wic: use kernel_dir to find systemd-efi bootloader
> * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
http://errors.yoctoproject.org/Errors/Details/135202/
"gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
"fix toolchain selection", which is included in OE-core 552bd78 and thus
should have been included in the build.
However, the error above was "Submitted on: 11/03/17 10:13", which was a
while ago and in particular before that fix.
Did ovmf really fail in the latest world build?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
@ 2017-03-29 8:35 ` Patrick Ohly
0 siblings, 0 replies; 11+ messages in thread
From: Patrick Ohly @ 2017-03-29 8:35 UTC (permalink / raw)
To: Martin Jansa
Cc: openembedded-devel, Patches and discussions about the oe-core layer
On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
That used OE-core 552bd78, if I read this right:
== Tested changes (not included in master yet) - openembedded-core ==
latest upstream commit:
552bd78 wic: use kernel_dir to find systemd-efi bootloader
> * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
http://errors.yoctoproject.org/Errors/Details/135202/
"gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
"fix toolchain selection", which is included in OE-core 552bd78 and thus
should have been included in the build.
However, the error above was "Submitted on: 11/03/17 10:13", which was a
while ago and in particular before that fix.
Did ovmf really fail in the latest world build?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: State of bitbake world, Failed tasks 2017-03-27
2017-03-29 8:35 ` [OE-core] " Patrick Ohly
@ 2017-03-29 9:14 ` Martin Jansa
-1 siblings, 0 replies; 11+ messages in thread
From: Martin Jansa @ 2017-03-29 9:14 UTC (permalink / raw)
To: Patrick Ohly
Cc: openembedded-devel, Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
>
> That used OE-core 552bd78, if I read this right:
>
> == Tested changes (not included in master yet) - openembedded-core ==
> latest upstream commit:
> 552bd78 wic: use kernel_dir to find systemd-efi bootloader
>
> > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
>
> http://errors.yoctoproject.org/Errors/Details/135202/
>
> "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> "fix toolchain selection", which is included in OE-core 552bd78 and thus
> should have been included in the build.
>
> However, the error above was "Submitted on: 11/03/17 10:13", which was a
> while ago and in particular before that fix.
>
> Did ovmf really fail in the latest world build?
The report shows:
http://errors.yoctoproject.org/Errors/Build/34933/
which leads to:
http://errors.yoctoproject.org/Errors/Details/138261/
Submitted on: 27/03/17 05:31
So yes it failed again, but this time with different error:
TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-oe-linux/gcc/i586-oe-linux/6.3.0/ld:
internal error in do_layout, at ../../gold/object.cc:1821
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
@ 2017-03-29 9:14 ` Martin Jansa
0 siblings, 0 replies; 11+ messages in thread
From: Martin Jansa @ 2017-03-29 9:14 UTC (permalink / raw)
To: Patrick Ohly
Cc: openembedded-devel, Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
>
> That used OE-core 552bd78, if I read this right:
>
> == Tested changes (not included in master yet) - openembedded-core ==
> latest upstream commit:
> 552bd78 wic: use kernel_dir to find systemd-efi bootloader
>
> > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
>
> http://errors.yoctoproject.org/Errors/Details/135202/
>
> "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> "fix toolchain selection", which is included in OE-core 552bd78 and thus
> should have been included in the build.
>
> However, the error above was "Submitted on: 11/03/17 10:13", which was a
> while ago and in particular before that fix.
>
> Did ovmf really fail in the latest world build?
The report shows:
http://errors.yoctoproject.org/Errors/Build/34933/
which leads to:
http://errors.yoctoproject.org/Errors/Details/138261/
Submitted on: 27/03/17 05:31
So yes it failed again, but this time with different error:
TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-oe-linux/gcc/i586-oe-linux/6.3.0/ld:
internal error in do_layout, at ../../gold/object.cc:1821
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: State of bitbake world, Failed tasks 2017-03-27
2017-03-29 9:14 ` [OE-core] " Martin Jansa
@ 2017-03-29 9:38 ` Patrick Ohly
-1 siblings, 0 replies; 11+ messages in thread
From: Patrick Ohly @ 2017-03-29 9:38 UTC (permalink / raw)
To: Martin Jansa
Cc: openembedded-devel, Patches and discussions about the oe-core layer
On Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:
> On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > > INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
> >
> > That used OE-core 552bd78, if I read this right:
> >
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit:
> > 552bd78 wic: use kernel_dir to find systemd-efi bootloader
> >
> > > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
> >
> > http://errors.yoctoproject.org/Errors/Details/135202/
> >
> > "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> > "fix toolchain selection", which is included in OE-core 552bd78 and thus
> > should have been included in the build.
> >
> > However, the error above was "Submitted on: 11/03/17 10:13", which was a
> > while ago and in particular before that fix.
> >
> > Did ovmf really fail in the latest world build?
>
> The report shows:
> http://errors.yoctoproject.org/Errors/Build/34933/
> which leads to:
>
> http://errors.yoctoproject.org/Errors/Details/138261/
> Submitted on: 27/03/17 05:31
Got it. I followed the wrong link at some point.
> So yes it failed again, but this time with different error:
> TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-oe-linux/gcc/i586-oe-linux/6.3.0/ld:
> internal error in do_layout, at ../../gold/object.cc:1821
Hmm, internal error in gold. Not sure what to do about that :-/
Can individual recipes choose to be built using the normal ld?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
@ 2017-03-29 9:38 ` Patrick Ohly
0 siblings, 0 replies; 11+ messages in thread
From: Patrick Ohly @ 2017-03-29 9:38 UTC (permalink / raw)
To: Martin Jansa
Cc: openembedded-devel, Patches and discussions about the oe-core layer
On Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:
> On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > > INFO: jenkins-job.sh-1.8.19 Complete log available at http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.report.20170328_014155.log
> >
> > That used OE-core 552bd78, if I read this right:
> >
> > == Tested changes (not included in master yet) - openembedded-core ==
> > latest upstream commit:
> > 552bd78 wic: use kernel_dir to find systemd-efi bootloader
> >
> > > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:do_compile
> >
> > http://errors.yoctoproject.org/Errors/Details/135202/
> >
> > "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> > "fix toolchain selection", which is included in OE-core 552bd78 and thus
> > should have been included in the build.
> >
> > However, the error above was "Submitted on: 11/03/17 10:13", which was a
> > while ago and in particular before that fix.
> >
> > Did ovmf really fail in the latest world build?
>
> The report shows:
> http://errors.yoctoproject.org/Errors/Build/34933/
> which leads to:
>
> http://errors.yoctoproject.org/Errors/Details/138261/
> Submitted on: 27/03/17 05:31
Got it. I followed the wrong link at some point.
> So yes it failed again, but this time with different error:
> TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-oe-linux/gcc/i586-oe-linux/6.3.0/ld:
> internal error in do_layout, at ../../gold/object.cc:1821
Hmm, internal error in gold. Not sure what to do about that :-/
Can individual recipes choose to be built using the normal ld?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: State of bitbake world, Failed tasks 2017-03-27
2017-03-29 9:38 ` [OE-core] " Patrick Ohly
@ 2017-03-29 10:14 ` Martin Jansa
-1 siblings, 0 replies; 11+ messages in thread
From: Martin Jansa @ 2017-03-29 10:14 UTC (permalink / raw)
To: Patrick Ohly
Cc: openembedded-devel, Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]
> Can individual recipes choose to be built using the normal ld?
yes, see example in:
meta/recipes-bsp/u-boot/u-boot.inc
meta/recipes-support/libunwind/libunwind_git.bb
but it was working with older binutils, so maybe worth tracking down where
it got borken.
On Wed, Mar 29, 2017 at 11:38 AM, Patrick Ohly <patrick.ohly@intel.com>
wrote:
> On Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:
> > On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> > > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > > > INFO: jenkins-job.sh-1.8.19 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.
> report.20170328_014155.log
> > >
> > > That used OE-core 552bd78, if I read this right:
> > >
> > > == Tested changes (not included in master yet) -
> openembedded-core ==
> > > latest upstream commit:
> > > 552bd78 wic: use kernel_dir to find systemd-efi bootloader
> > >
> > > > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:
> do_compile
> > >
> > > http://errors.yoctoproject.org/Errors/Details/135202/
> > >
> > > "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> > > "fix toolchain selection", which is included in OE-core 552bd78 and
> thus
> > > should have been included in the build.
> > >
> > > However, the error above was "Submitted on: 11/03/17 10:13", which was
> a
> > > while ago and in particular before that fix.
> > >
> > > Did ovmf really fail in the latest world build?
> >
> > The report shows:
> > http://errors.yoctoproject.org/Errors/Build/34933/
> > which leads to:
> >
> > http://errors.yoctoproject.org/Errors/Details/138261/
> > Submitted on: 27/03/17 05:31
>
> Got it. I followed the wrong link at some point.
>
> > So yes it failed again, but this time with different error:
> > TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-
> sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-
> oe-linux/gcc/i586-oe-linux/6.3.0/ld:
> > internal error in do_layout, at ../../gold/object.cc:1821
>
> Hmm, internal error in gold. Not sure what to do about that :-/
>
> Can individual recipes choose to be built using the normal ld?
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 4183 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
@ 2017-03-29 10:14 ` Martin Jansa
0 siblings, 0 replies; 11+ messages in thread
From: Martin Jansa @ 2017-03-29 10:14 UTC (permalink / raw)
To: Patrick Ohly
Cc: openembedded-devel, Patches and discussions about the oe-core layer
> Can individual recipes choose to be built using the normal ld?
yes, see example in:
meta/recipes-bsp/u-boot/u-boot.inc
meta/recipes-support/libunwind/libunwind_git.bb
but it was working with older binutils, so maybe worth tracking down where
it got borken.
On Wed, Mar 29, 2017 at 11:38 AM, Patrick Ohly <patrick.ohly@intel.com>
wrote:
> On Wed, 2017-03-29 at 11:14 +0200, Martin Jansa wrote:
> > On Wed, Mar 29, 2017 at 10:35:23AM +0200, Patrick Ohly wrote:
> > > On Wed, 2017-03-29 at 09:23 +0200, Martin Jansa wrote:
> > > > INFO: jenkins-job.sh-1.8.19 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/pyro/log.
> report.20170328_014155.log
> > >
> > > That used OE-core 552bd78, if I read this right:
> > >
> > > == Tested changes (not included in master yet) -
> openembedded-core ==
> > > latest upstream commit:
> > > 552bd78 wic: use kernel_dir to find systemd-efi bootloader
> > >
> > > > * openembedded-core/meta/recipes-core/ovmf/ovmf_git.bb:
> do_compile
> > >
> > > http://errors.yoctoproject.org/Errors/Details/135202/
> > >
> > > "gcc-ar: not found" - that should have been fixed by OE-core 23a12d87a6
> > > "fix toolchain selection", which is included in OE-core 552bd78 and
> thus
> > > should have been included in the build.
> > >
> > > However, the error above was "Submitted on: 11/03/17 10:13", which was
> a
> > > while ago and in particular before that fix.
> > >
> > > Did ovmf really fail in the latest world build?
> >
> > The report shows:
> > http://errors.yoctoproject.org/Errors/Build/34933/
> > which leads to:
> >
> > http://errors.yoctoproject.org/Errors/Details/138261/
> > Submitted on: 27/03/17 05:31
>
> Got it. I followed the wrong link at some point.
>
> > So yes it failed again, but this time with different error:
> > TOPDIR/tmp-glibc/work/i586-oe-linux/ovmf/git-r0/recipe-
> sysroot-native/usr/bin/i586-oe-linux/../../libexec/i586-
> oe-linux/gcc/i586-oe-linux/6.3.0/ld:
> > internal error in do_layout, at ../../gold/object.cc:1821
>
> Hmm, internal error in gold. Not sure what to do about that :-/
>
> Can individual recipes choose to be built using the normal ld?
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: State of bitbake world, Failed tasks 2017-03-27
2017-03-29 10:14 ` [OE-core] " Martin Jansa
@ 2017-03-29 11:19 ` Patrick Ohly
-1 siblings, 0 replies; 11+ messages in thread
From: Patrick Ohly @ 2017-03-29 11:19 UTC (permalink / raw)
To: Martin Jansa
Cc: openembedded-devel, Patches and discussions about the oe-core layer
On Wed, 2017-03-29 at 12:14 +0200, Martin Jansa wrote:
> > Can individual recipes choose to be built using the normal ld?
>
>
>
> yes, see example in:
> meta/recipes-bsp/u-boot/u-boot.inc
>
> meta/recipes-support/libunwind/libunwind_git.bb
Thanks. I'll try to do something similar.
> but it was working with older binutils, so maybe worth tracking down
> where it got borken.
Before my OE-core fix, it was always using /usr/bin/gcc and thus ld. Now
that it actually uses the compiler intended for the target, it ends up
using gold, which fails.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
@ 2017-03-29 11:19 ` Patrick Ohly
0 siblings, 0 replies; 11+ messages in thread
From: Patrick Ohly @ 2017-03-29 11:19 UTC (permalink / raw)
To: Martin Jansa
Cc: openembedded-devel, Patches and discussions about the oe-core layer
On Wed, 2017-03-29 at 12:14 +0200, Martin Jansa wrote:
> > Can individual recipes choose to be built using the normal ld?
>
>
>
> yes, see example in:
> meta/recipes-bsp/u-boot/u-boot.inc
>
> meta/recipes-support/libunwind/libunwind_git.bb
Thanks. I'll try to do something similar.
> but it was working with older binutils, so maybe worth tracking down
> where it got borken.
Before my OE-core fix, it was always using /usr/bin/gcc and thus ld. Now
that it actually uses the compiler intended for the target, it ends up
using gold, which fails.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2017-03-29 11:19 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-29 7:23 State of bitbake world, Failed tasks 2017-03-27 Martin Jansa
2017-03-29 8:35 ` Patrick Ohly
2017-03-29 8:35 ` [OE-core] " Patrick Ohly
2017-03-29 9:14 ` Martin Jansa
2017-03-29 9:14 ` [OE-core] " Martin Jansa
2017-03-29 9:38 ` Patrick Ohly
2017-03-29 9:38 ` [OE-core] " Patrick Ohly
2017-03-29 10:14 ` Martin Jansa
2017-03-29 10:14 ` [OE-core] " Martin Jansa
2017-03-29 11:19 ` Patrick Ohly
2017-03-29 11:19 ` [OE-core] " Patrick Ohly
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.