From: Martin Jansa <martin.jansa@gmail.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org,
openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Andrei Dinu : libffi upgrade to 3.0.11
Date: Sat, 15 Sep 2012 19:39:05 +0200 [thread overview]
Message-ID: <20120915173905.GD11051@jama.jama.net> (raw)
In-Reply-To: <20120915172816.GC11051@jama.jama.net>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
On Sat, Sep 15, 2012 at 07:28:16PM +0200, Martin Jansa wrote:
> On Sat, Sep 15, 2012 at 06:23:37PM +0100, Phil Blundell wrote:
> > On Sat, 2012-09-15 at 18:20 +0200, Martin Jansa wrote:
> > > This changes .so name from libffi5 to libffi6, breaking every recipe
> > > depending on libffi when someone is using debian.bbclass.
> >
> > How exactly do the recipes break? The whole point of debian.bbclass is
> > to avoid breakage when this happens by making libffi5 and libffi6
> > parallel installable. If that isn't working then there is clearly a bug
> > somewhere and we should fix that.
>
> libffi5 is no longer in feed, so if you try to install something from
> feed which still has libffi5 in depends it will fail.
>
> Cheers,
also e.g. navit is using librsvg-native to create .png from .svg and
fails now
|
SRCDIR=/OE/shr-core/tmp-eglibc/work/armv4t-oe-linux-gnueabi/navit-1_0.2.0+svnr5159-r11.3/navit/navit/xpm
BUILDDIR=/OE/shr-core/tmp-eglibc/work/armv4t-oe-linux-gnueabi/navit-1_0.2.0+svnr5159-r11.3/navit/navit/xpm
./navit_svg2png
"/OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/rsvg-convert"
"nav_destination_wh_96_96.png"
| /OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/rsvg-convert:
error while loading shared libraries: libffi.so.5: cannot open shared
object file: No such file or directory
Fortunately navit.do_install finds that some mandatory .png files are
missing and fails too (before creating invalid .ipk in feed).
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-09-15 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120914085706.2CBFC103C3@opal>
2012-09-15 16:20 ` [oe-commits] Andrei Dinu : libffi upgrade to 3.0.11 Martin Jansa
[not found] ` <CAK18fxGHn8aMu9Y926M2r9RQULR2VTOciBJkVD5S9awBV_j7-Q@mail.gmail.com>
2012-09-15 16:37 ` [O-core] " Martin Jansa
2012-09-17 10:57 ` Martin Jansa
2012-09-15 17:23 ` Phil Blundell
2012-09-15 17:28 ` Martin Jansa
2012-09-15 17:39 ` Martin Jansa [this message]
2012-09-15 20:39 ` Phil Blundell
2012-09-16 14:30 ` Martin Jansa
2012-09-16 18:47 ` [PATCH] recipes: bump PR to rebuild after libffi5 -> libffi6 Martin Jansa
2012-09-17 10:54 ` [PATCH] recipes: few more PR bumps " Martin Jansa
2012-09-17 17:17 ` [PATCH] libtelepathy: PR bump " Martin Jansa
2012-09-19 17:45 ` Saul Wold
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=20120915173905.GD11051@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=philb@gnu.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