All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gdk-pixbuf: Avoid rebuild failures
Date: Thu, 24 Sep 2015 08:27:53 -0300	[thread overview]
Message-ID: <CAP9ODKrBa6oiFm2Fj1XxtH5m2gx=6nSg4OhEs+s_KjgvAgFaFg@mail.gmail.com> (raw)
In-Reply-To: <1443047565.19044.44.camel@linuxfoundation.org>

Hello Richard,

Thanks for hunting this bug, this was very annoying and hard to
figure. It does seem to address the issue in our builder.

On Wed, Sep 23, 2015 at 7:32 PM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> If gdkpixbuf-native rebuilds and there are stale (broken) modules lying around,
> it can fail to run the postinst. E.g. svg links to harfbuzz and if harfbuzz is
> removed from the sysroot but the svg loader isn't, we get a symbol linking issue.
>
> The reproducer is along the lines of build gdk-pixbuf-native along
> with harfbuzz-native and librsvg-native, then make a small change to the
> gdk-pixbuf recipe that would cause it to rebuild, clean harfbuzz-native
> and then build gdk-pixbuf.
>
> To fix this, when we install gdk-pixbuf, we wipe out any previous loaders.
> The idea is that gdk would always come first and anything else installing
> itself will come later and rerun the postinst if needed. We can therefore
> just remove any other loaders.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Acked-by: Otavio Salvador <otavio@ossystems.com.br>

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  parent reply	other threads:[~2015-09-24 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 22:32 [PATCH] gdk-pixbuf: Avoid rebuild failures Richard Purdie
2015-09-23 22:54 ` Gary Thomas
2015-09-24  6:35   ` Richard Purdie
2015-09-24 11:27 ` Otavio Salvador [this message]
2015-09-24 21:40   ` Richard Purdie
2015-09-25 18:12     ` Otavio Salvador

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='CAP9ODKrBa6oiFm2Fj1XxtH5m2gx=6nSg4OhEs+s_KjgvAgFaFg@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.