From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <kergoth@gmail.com>,
"Bystricky, Juro" <juro.bystricky@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [master][PATCH] gcc-cross{, -canadian}: remove --with-linker-hash-style
Date: Mon, 09 May 2016 23:16:30 +0100 [thread overview]
Message-ID: <1462832190.21831.156.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZAN=jh=+8PMVw2YMw41Aax1hmssjOVe24SG9XhjB4HgQuwQ@mail.gmail.com>
On Mon, 2016-05-09 at 09:39 -0700, Christopher Larson wrote:
>
>
> On Mon, May 9, 2016 at 9:35 AM, Bystricky, Juro <
> juro.bystricky@intel.com> wrote:
> > Two additional GNU_HASH related errors were observed (breaking some
> > builds) that seem to be related to the patch:
> >
> > ERROR: bash-3.2.48-r11 do_package_qa: QA Issue: No GNU_HASH in the
> > elf binary: '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly
> > -non-gpl3/build/build/tmp/work/i586-poky-linux/bash/3.2.48
> > -r11/packages-split/bash-ptest/usr/lib/bash/ptest/tests/recho'
> > No GNU_HASH in the elf binary: '/home/pokybuild/yocto
> > -autobuilder/yocto-worker/nightly-non
> > -gpl3/build/build/tmp/work/i586-poky-linux/bash/3.2.48-r11/packages
> > -split/bash-ptest/usr/lib/bash/ptest/tests/zecho'
> > No GNU_HASH in the elf binary: '/home/pokybuild/yocto
> > -autobuilder/yocto-worker/nightly-non
> > -gpl3/build/build/tmp/work/i586-poky-linux/bash/3.2.48-r11/packages
> > -split/bash-ptest/usr/lib/bash/ptest/tests/printenv' [ldflags]
> > ERROR: bash-3.2.48-r11 do_package_qa: QA run found fatal errors.
> > Please consider fixing them.
> >
> >
> > ERROR: service-0.1-r0 do_package_qa: QA Issue: No GNU_HASH in the
> > elf binary: '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly
> > -qa-skeleton/build/build/tmp/work/core2-64-poky-linux/service/0.1
> > -r0/packages-split/service/usr/sbin/skeleton-test' [ldflags]
> >
> Huh, I must not have had ptest enabled in my test builds. Thanks,
> will take a look.
The above is an older gplv2 recipe failure which is probably why you
didn't see it.
I'm afraid there were more. pseudo:
https://autobuilder.yoctoproject.org/main/builders/build-appliance/buil
ds/747/steps/BuildImages_1/logs/stdio
qt-x11-free:
https://autobuilder.yoctoproject.or
g/main/builders/nightly-arm-lsb/builds/734/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/buil
ds/744/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/b
uilds/779/steps/BuildImages/logs/stdio
service in qa-skeleton:
https://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/
builds/753/steps/BuildImages/logs/stdio
ruby and mkefiimage:
https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/build
s/104/steps/BuildImages/logs/stdio
(selftest also showed mkefimage failure)
Cheers,
Richard
next prev parent reply other threads:[~2016-05-09 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 20:09 [master][PATCH] gcc-cross{, -canadian}: remove --with-linker-hash-style Christopher Larson
2016-05-02 20:34 ` Khem Raj
2016-05-02 20:37 ` Christopher Larson
2016-05-02 21:37 ` Khem Raj
2016-05-03 2:53 ` Christopher Larson
2016-05-03 3:01 ` Khem Raj
2016-05-03 3:05 ` Christopher Larson
2016-05-03 8:09 ` Martin Jansa
2016-05-03 9:11 ` Anders Darander
2016-05-03 16:07 ` Christopher Larson
2016-05-03 18:13 ` Denys Dmytriyenko
2016-05-04 14:01 ` Burton, Ross
2016-05-04 19:11 ` Christopher Larson
2016-05-09 16:35 ` Bystricky, Juro
2016-05-09 16:39 ` Christopher Larson
2016-05-09 22:16 ` Richard Purdie [this message]
2016-05-09 22:34 ` Christopher Larson
2016-05-09 22:41 ` Christopher Larson
2016-05-09 22:54 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1462832190.21831.156.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=juro.bystricky@intel.com \
--cc=kergoth@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.