From: Sinan Kaya <Okaya@kernel.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v1] postinst-intercepts: check tool presence in intercept hooks
Date: Sun, 30 Jun 2019 12:56:18 -0400 [thread overview]
Message-ID: <879d6ab4-5948-61ac-d783-401d660b0e94@kernel.org> (raw)
In-Reply-To: <CANNYZj-Oow=4m4A1a6k+Mcjo6qf5cnCAR5_OGrhitM1-XqZALg@mail.gmail.com>
On 6/27/2019 4:46 AM, Alexander Kanavin wrote:
> This issue showed up in thud using core-image-minimal. It was not there
> on sumo.
>
>
> If you can provide steps to reproduce, it could help. Please start with
> a git checkout of poky thud branch.
>
Issue in only happening on the build machine with docker using ubuntu
16.04 as a baseline.
I'm having hard-time reproducing on my development machine.
My cursory web search says that I'm not the only one hitting this issue
and people have mysteriously solved this issue.
https://github.com/riscv/meta-riscv/issues/26
The following matches what I see on the build machine.
"/update_pixbuf_cache: 8:
/home/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/intercept_scripts-2c03b46bc7941049a88b6c1719c35aade81b0ce5490421e7cca768bf8beb0d01
/update_pixbuf_cache: cannot create
/home//riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-image-full-cmdline/1.0-r0/rootfs/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/../loaders.cache:
Directory nonexistent"
next prev parent reply other threads:[~2019-06-30 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 22:13 [PATCH v1] postinst-intercepts: check tool presence in intercept hooks Sinan Kaya
2019-06-26 2:27 ` ChenQi
2019-06-26 8:59 ` Alexander Kanavin
2019-06-26 17:33 ` Sinan Kaya
2019-06-26 18:10 ` Alexander Kanavin
2019-06-26 21:21 ` Richard Purdie
2019-06-26 22:57 ` Sinan Kaya
2019-06-27 8:46 ` Alexander Kanavin
2019-06-30 16:56 ` Sinan Kaya [this message]
2019-06-30 21:54 ` richard.purdie
2019-07-01 1:38 ` Sinan Kaya
2019-06-27 8:57 ` 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=879d6ab4-5948-61ac-d783-401d660b0e94@kernel.org \
--to=okaya@kernel.org \
--cc=alex.kanavin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox