From: Martin Jansa <martin.jansa@gmail.com>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: openembedded-commits@lists.openembedded.org,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [O-core] [oe-commits] Andrei Dinu : libffi upgrade to 3.0.11
Date: Mon, 17 Sep 2012 12:57:52 +0200 [thread overview]
Message-ID: <20120917105752.GD3628@jama.jama.net> (raw)
In-Reply-To: <20120915163739.GB11051@jama.jama.net>
[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]
On Sat, Sep 15, 2012 at 06:37:39PM +0200, Martin Jansa wrote:
> On Sat, Sep 15, 2012 at 07:22:43PM +0300, Andrei Gherzan wrote:
> > On Sat, Sep 15, 2012 at 7:20 PM, Martin Jansa <martin.jansa@gmail.com>wrote:
> >
> > > On Fri, Sep 14, 2012 at 08:57:06AM +0000, git@git.openembedded.org wrote:
> > > > Module: openembedded-core.git
> > > > Branch: master
> > > > Commit: 3e40136e8bd13b17b6d88b6acfb5ed162bb8d96a
> > > > URL:
> > > http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=3e40136e8bd13b17b6d88b6acfb5ed162bb8d96a
> > > >
> > > > Author: Andrei Dinu <andrei.adrianx.dinu@intel.com>
> > > > Date: Thu Sep 13 11:26:45 2012 +0300
> > > >
> > > > libffi upgrade to 3.0.11
> > >
> > > This changes .so name from libffi5 to libffi6, breaking every recipe
> > > depending on libffi when someone is using debian.bbclass.
> > >
> > > This list of 374 packages is probably not complete, just what I have
> > > built before.
> > >
> > > http://build.shr-project.org/tests/jama/libffi5.pkgs
> >
> >
> > Confirmed. Just ran into this with glib-2.0.
>
> Something like:
> | /OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/4.7.2/ld: warning: libffi.so.5, needed by /OE/shr-core/tmp-eglibc/sysroots/q
> emux86-64/usr/lib/libgobject-2.0.so, not found (try using -rpath or -rpath-link)
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_void'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_double'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_prep_cif'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_sint32'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_float'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_uint64'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_sint64'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_pointer'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_type_uint32'
> | /OE/shr-core/tmp-eglibc/sysroots/qemux86-64/usr/lib/libgobject-2.0.so: undefined reference to `ffi_call'
>
> That's easy to fix by manual rebuild, but for runtime packages we need those PR bumps :/.
>
> I'll PR bump recipes (from my list) in meta-oe and meta-smartphone layers,
> but leave oe-core for someone else.
PR bumps for recipes from my list sent to oe-core too, but again it's
probably not complete (only stuff included in one of images I build).
Someone should build world-image to test the rest..
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-17 11:10 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 [this message]
2012-09-15 17:23 ` Phil Blundell
2012-09-15 17:28 ` Martin Jansa
2012-09-15 17:39 ` Martin Jansa
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=20120917105752.GD3628@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=andrei@gherzan.ro \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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