From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Error building gdk-pixbuf-native
Date: Tue, 22 Sep 2015 13:13:27 -0600 [thread overview]
Message-ID: <5601A857.7060404@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKpQDhCL9QbACgMRzV=N_Z7476a1_OxkhV7z0O7PfVd_rQ@mail.gmail.com>
On 2015-09-22 12:38, Otavio Salvador wrote:
> On Tue, Sep 22, 2015 at 3:14 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2015-09-22 12:05, Otavio Salvador wrote:
>>>
>>> On Tue, Sep 22, 2015 at 12:28 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>
>>>> When building gdk-pixbuf-native, I got this error:
>>>> | DEBUG: Staging files from
>>>>
>>>> /home/local/rpi2_2015-03-05/tmp/work/i686-linux/gdk-pixbuf-native/2.30.8-r0/sysroot-destdir/home/local/rpi2_2015-03-05/tmp/sysroots/i686-linux
>>>> to /home/local/rpi2_2015-03-05/tmp/sysroots/i686-linux
>>>> | DEBUG: Executing shell function pixbufcache_sstate_postinst
>>>> | g_module_open() failed for
>>>>
>>>> /home/local/rpi2_2015-03-05/tmp/sysroots/i686-linux/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so:
>>>> libharfbuzz.so.0: cannot open shared object file: No such file or
>>>> directory
>>>>
>>>> It seems that [at least] gdk-pixbuf-native needs harfbuzz-native
>>>> I looked at the recipe, but it's not 100% obvious to me how to
>>>> add this, especially w.r.t. all of the PACKAGECONFIG options.
>>>>
>>>> Guidance?
>>>
>>>
>>> I had similar failures[1] at O.S. Systems autobuilder and rebuilding
>>> made it work.
>>>
>>> 1.
>>> http://ci.ossystems.com.br/view/FSL%20Community%20BSP%20-%20master-next/job/fsl-community-bsp-master-next_wayland-imx28evk/827/console
>>>
>>> The builds are now succeeding but I did no change to fix it. This
>>> seems like a race for me.
>>>
>>> I tried very hard to reproduce the issue locally at my laptop without
>>> success. Do you can reliably reproduce it?
>>>
>>
>> Yes, I had a full tree and this rebuild was kicked off by a meta-data
>> update. Once it happened, I tried this:
>> % bitbake harfbuzz-native gdk-pixbuf-native -c cleansstate
>> % bitbake gdk-pixbuf-native
>> failed. However the manual sequence
>> % bitbake harfbuzz-native
>> % bitbake gdk-pixbuf-native
>> succeeded.
>
> I still do not reproduce it :-(
>
It seems to be a host [contamination?] issue. I get this error
on a build host that does not have libharfbuzz.so installed. On
a build host which does, there is no error.
Note that it is only for the native package, so perhaps that's
where the dependency needs to be updated/checked (hence my original
query)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-09-22 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 15:28 Error building gdk-pixbuf-native Gary Thomas
2015-09-22 18:05 ` Otavio Salvador
2015-09-22 18:14 ` Gary Thomas
2015-09-22 18:38 ` Otavio Salvador
2015-09-22 19:13 ` Gary Thomas [this message]
2015-09-22 20:52 ` Otavio Salvador
2015-09-22 23:23 ` Khem Raj
2015-09-22 23:28 ` Otavio Salvador
2015-09-22 23:30 ` Khem Raj
2015-09-23 0:28 ` Otavio Salvador
2015-09-23 22:25 ` Richard Purdie
2015-09-23 12:15 ` Burton, Ross
2015-09-23 12:24 ` Gary Thomas
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=5601A857.7060404@mlbassoc.com \
--to=gary@mlbassoc.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.