From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: native sysroot race with rpmbuild
Date: Mon, 14 Aug 2017 11:38:18 +0100 [thread overview]
Message-ID: <1502707098.13978.3.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAHiDW_EycsMUfCykDicgHuVzykCT0YYQHE9EY8i6yFqJsbbSJQ@mail.gmail.com>
On Mon, 2017-08-14 at 11:33 +0300, Jussi Kukkonen wrote:
> I'm seeing lots of this failure in my last build:
>
> | DEBUG: PKGWRITEDIR: /mnt/extra-ssd/tmp/work/all-poky-linux/adwaita-
> icon-theme/3.24.0-r0/deploy-rpms/noarch
> | DEBUG: SITE files ['endian-little', 'bit-32', 'common-linux',
> 'common-glibc', 'allarch-linux', 'common']
> | DEBUG: Executing shell function BUILDSPEC
> | /mnt/extra-ssd/tmp/work/all-poky-linux/adwaita-icon-theme/3.24.0-
> r0/recipe-sysroot-native/usr/bin/rpmbuild: error while loading shared
> libraries: libdw.so.1: cannot open shared object file: No such file
> or directory
> | WARNING: exit code 127 from a shell command.
> | DEBUG: Python function do_package_rpm finished
> | DEBUG: Python function do_package_write_rpm finished
> | ERROR: Function failed: BUILDSPEC (log file is located at
> /mnt/extra-ssd/tmp/work/all-poky-linux/adwaita-icon-theme/3.24.0-
> r0/temp/log.do_package_write_rpm.21827)
> ERROR: Task (/home/jku/src/poky/meta/recipes-gnome/gnome/adwaita-
> icon-theme_3.24.0.bb:do_package_write_rpm) failed with exit code '1'
>
> * libdw.so.1 isn't found when rpmbuild runs
> * seems to be a race as the library is there when I check (and
> building again works)
> * Seems to mostly happen with allarch recipes (maybe they're just
> fast enough): sysvinit-inittab, adwaita, xcursor-transparent-theme,
> iso-codes
>
> Any ideas?
Could you tar up /mnt/extra-ssd/tmp/work/all-poky-linux/adwaita-icon-
theme/3.24.0-r0/temp/log* and share somewhere please?
Not sure what is going on there, it seems odd :( What other tasks were
running when this happened?
I had a go at reproducing this locally but couldn't.
Cheers,
Richard
next prev parent reply other threads:[~2017-08-14 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 8:33 native sysroot race with rpmbuild Jussi Kukkonen
2017-08-14 10:38 ` Richard Purdie [this message]
2017-08-14 10:55 ` Jussi Kukkonen
2017-08-14 11:02 ` Richard Purdie
2017-08-26 22:36 ` 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=1502707098.13978.3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jussi.kukkonen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox