View previous topic :: View next topic |
Author |
Message |
bukich n00b
Joined: 11 Apr 2011 Posts: 12
|
Posted: Tue Apr 19, 2011 7:38 am Post subject: [SOLVED] Can't update gentoo |
|
|
Hi,
I'm trying to update my gentoo system but I can't finish it:
# emerge --update --deep world
.
.
.
.
._gen/telepathy-interfaces.h:1325: Warning: TelepathyGLib: tp_iface_quark_client_interface_requests: Couldn't find corresponding enumeration
_gen/telepathy-interfaces.h:1334: Warning: TelepathyGLib: tp_iface_quark_debug: Couldn't find corresponding enumeration
_gen/telepathy-interfaces.h:1346: Warning: TelepathyGLib: tp_iface_quark_authentication_tls_certificate: Couldn't find corresponding enumeration
Kludged around GNOME Bug #629668
Kludged around GNOME Bug #629668
Kludged around GNOME Bug #629668
Kludged around GNOME Bug #616375
../libtool --mode=execute \
/usr/bin/g-ir-compiler \
--includedir=. \
--includedir=. \
TelepathyGLib-0.12.gir -o TelepathyGLib-0.12.typelib
/usr/bin/g-ir-compiler: error while loading shared libraries: libffi.so.5: cannot open shared object file: No such file or directory
make[3]: *** [TelepathyGLib-0.12.typelib] Error 127
make[3]: Leaving directory `/var/tmp/portage/net-libs/telepathy-glib-0.14.4/work/telepathy-glib-0.14.4/telepathy-glib'
make[2]: *** [all] Error 2
rm _gen/tp-spec-generic.xml _gen/tp-spec-media-session-handler.xml _gen/tp-spec-channel-dispatcher.xml _gen/tp-spec-channel.xml _gen/tp-spec-dbus-daemon.xml _gen/tp-spec-connection.xml _gen/tp-spec-account.xml _gen/tp-spec-account-manager.xml _gen/tp-spec-protocol.xml _gen/tp-spec-tls-cert.xml _gen/tp-spec-channel-request.xml _gen/tp-spec-channel-dispatch-operation.xml _gen/tp-spec-debug.xml _gen/tp-spec-connection-manager.xml _gen/tp-spec-client.xml _gen/tp-spec-media-stream-handler.xml
make[2]: Leaving directory `/var/tmp/portage/net-libs/telepathy-glib-0.14.4/work/telepathy-glib-0.14.4/telepathy-glib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/net-libs/telepathy-glib-0.14.4/work/telepathy-glib-0.14.4'
make: *** [all] Error 2
emake failed
* ERROR: net-libs/telepathy-glib-0.14.4 failed (compile phase):
* emake failed
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3039: Called _eapi2_src_compile
* ebuild.sh, line 665: Called die
* The specific snippet of code:
* emake || die "emake failed"
*
* If you need support, post the output of 'emerge --info =net-libs/telepathy-glib-0.14.4',
* the complete build log and the output of 'emerge -pqv =net-libs/telepathy-glib-0.14.4'.
* The complete build log is located at '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/temp/environment'.
* S: '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/work/telepathy-glib-0.14.4'
>>> Failed to emerge net-libs/telepathy-glib-0.14.4, Log file:
>>> '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/temp/build.log'
* Messages for package net-libs/telepathy-glib-0.14.4:
* ERROR: net-libs/telepathy-glib-0.14.4 failed (compile phase):
* emake failed
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3039: Called _eapi2_src_compile
* ebuild.sh, line 665: Called die
* The specific snippet of code:
* emake || die "emake failed"
*
* If you need support, post the output of 'emerge --info =net-libs/telepathy-glib-0.14.4',
* the complete build log and the output of 'emerge -pqv =net-libs/telepathy-glib-0.14.4'.
* The complete build log is located at '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/temp/environment'.
* S: '/var/tmp/portage/net-libs/telepathy-glib-0.14.4/work/telepathy-glib-0.14.4'
* GNU info directory index is up-to-date.
* After world updates, it is important to remove obsolete packages with
* emerge --depclean. Refer to `man emerge` for more information.
It seems that the problem is this:
/usr/bin/g-ir-compiler: error while loading shared libraries: libffi.so.5: cannot open shared object file: No such file or directory
I've checked and I have /usr/bin/g-ir-compiler
# ldd /usr/bin/g-ir-compiler
linux-vdso.so.1 => (0x00007fff6c9ff000)
libgirepository-1.0.so.1 => /usr/lib64/libgirepository-1.0.so.1 (0x00007f7d8878c000)
libm.so.6 => /lib64/libm.so.6 (0x00007f7d8850a000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f7d881df000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f7d87f8d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7d87d70000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f7d87a55000)
libffi.so.5 => not found
libc.so.6 => /lib64/libc.so.6 (0x00007f7d876ce000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f7d874b8000)
libz.so.1 => /lib64/libz.so.1 (0x00007f7d872a0000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f7d8709c000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f7d86e97000)
librt.so.1 => /lib64/librt.so.1 (0x00007f7d86c8e000)
libffi.so.5 => not found
libdl.so.2 => /lib64/libdl.so.2 (0x00007f7d86a8a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7d889be000)
Regards
Last edited by bukich on Wed Apr 20, 2011 8:09 am; edited 1 time in total |
|
Back to top |
|
|
Arkhelion Apprentice
Joined: 07 Sep 2010 Posts: 151 Location: France
|
Posted: Tue Apr 19, 2011 7:51 am Post subject: |
|
|
Hello,
It seems it can't find dev-libs/libffi. Try to re-emerge it (python should depend on it, AFAIK)
EDIT : you may have to recompile gobject-introspection for g-ir-compiler to link against it (or revdep-rebuild should do it for you) _________________ Arkhelion |
|
Back to top |
|
|
bukich n00b
Joined: 11 Apr 2011 Posts: 12
|
Posted: Tue Apr 19, 2011 7:56 am Post subject: |
|
|
I had issue before with python.
After upgrade default python was 3.1, I've made eselect python 1 (python 2.7)
and made python-udapte
But now when I'm trying to emerge python it gives me again python 3.1
Strange |
|
Back to top |
|
|
Arkhelion Apprentice
Joined: 07 Sep 2010 Posts: 151 Location: France
|
Posted: Tue Apr 19, 2011 8:26 am Post subject: |
|
|
I have both python-2.7 and python-3.1 installed, but default python should not automatically switch unless you eselect another slot.
python-updater should also be run each time you have a python update. BTW tell us if reemerging libffi (with oneshot so it won't get in world) and gobject-introspection fixes your issue.
EDIT: If it proposes you to emerge python-3.1 it should be marked as [ NS ] as in New Slot so emerging it should'nt change your default python and you should still have bot python-2.7 and python-3.1 when the emerge ends. _________________ Arkhelion |
|
Back to top |
|
|
bukich n00b
Joined: 11 Apr 2011 Posts: 12
|
Posted: Tue Apr 19, 2011 8:29 am Post subject: |
|
|
reemerging libffi doesn't solve the problem
also reemerging python,libtool
Problem is still the same |
|
Back to top |
|
|
Arkhelion Apprentice
Joined: 07 Sep 2010 Posts: 151 Location: France
|
Posted: Tue Apr 19, 2011 8:52 am Post subject: |
|
|
Check if /usr/lib/libffi.so.5 exists, if it's there, reemerge gobject-introspection in order to have g-ir-compiler linked against it. _________________ Arkhelion |
|
Back to top |
|
|
bukich n00b
Joined: 11 Apr 2011 Posts: 12
|
Posted: Tue Apr 19, 2011 9:35 am Post subject: |
|
|
It seems that I have:
# ls -la /usr/lib/libffi*
lrwxrwxrwx 1 root root 15 Apr 19 11:05 /usr/lib/libffi.so -> libffi.so.6.0.0
lrwxrwxrwx 1 root root 15 Apr 19 11:05 /usr/lib/libffi.so.6 -> libffi.so.6.0.0
-rwxr-xr-x 1 root root 30880 Apr 19 11:05 /usr/lib/libffi.so.6.0.0 |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Apr 19, 2011 10:58 pm Post subject: |
|
|
Code: | emerge lafilefixer
lafilefixer --justfixit |
if not done recently:
Code: | emerge perl-cleaner
perl-cleaner all |
might be worth it. _________________ Defund the FCC. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21631
|
Posted: Wed Apr 20, 2011 2:28 am Post subject: |
|
|
The presence of libffi.so.6 says that the library was upgraded, but not all programs linked to the old version have been rebuilt. A revdep-rebuild is the most likely solution at this point. Rebuilding dev-libs/libffi does not help because libffi.so.5 is part of an outdated version of the package, and rebuilding instead reinstalls libffi.so.6. |
|
Back to top |
|
|
bukich n00b
Joined: 11 Apr 2011 Posts: 12
|
Posted: Wed Apr 20, 2011 8:09 am Post subject: |
|
|
Hi Hu,
Thanks again for your valuable support, revdep-rebuild fix the issue
Regards |
|
Back to top |
|
|
Helena Veteran
Joined: 02 Apr 2003 Posts: 1114 Location: Den Dolder, The Netherlands
|
Posted: Sun Sep 04, 2011 6:34 am Post subject: |
|
|
Hu wrote: | The presence of libffi.so.6 says that the library was upgraded, but not all programs linked to the old version have been rebuilt. A revdep-rebuild is the most likely solution at this point. Rebuilding dev-libs/libffi does not help because libffi.so.5 is part of an outdated version of the package, and rebuilding instead reinstalls libffi.so.6. |
There's something strange going on here.
While being on arch ~amd64, 6 months later I would assume that libffi.so.6 would be standard. It is not. With the help of this topic I was able to solve my own update problems including gdk-pixbuf and chromium by a revdep-rebuild, which resulted in Code: | emerge --oneshot --complete-graph dev-lang/python:2.7 dev-lang/python:3.2 dev-libs/gobject-introspection:0 dev-python/pygobject:2 sys-devel/llvm:0 |
However, unlike your suggestion, libffi.so.6 is not installed and libffi.so.5 remains (I even rebuilt dev-libs/libffi-3.0.10 but that didn't change a thing...). Now I'm puzzled as to why this g-ir-compiler expects and even depends on a future version of a library?? |
|
Back to top |
|
|
Da_G n00b
Joined: 01 Nov 2006 Posts: 12
|
Posted: Wed Sep 07, 2011 9:11 pm Post subject: |
|
|
Same thing;
Had a bunch of apps compiled against libffi.so.6, did a emerge -uavDN world update today and libffi "upgraded" to libffi.so.5, breaking the aforementioned apps, revdep-rebuild cleaned it up, but why? |
|
Back to top |
|
|
bzImage n00b
Joined: 14 Oct 2002 Posts: 35
|
Posted: Sat Sep 17, 2011 5:39 am Post subject: |
|
|
Same thing here..
after
emerge --sync
and
emerge -uDNa world
i got:
Babl-0.1.gir -o Babl-0.1.typelib
/usr/bin/g-ir-compiler: error while loading shared libraries: libffi.so.6: cannot open shared object file: No such file or directory
make[3]: *** [Babl-0.1.typelib] Error 127
So Babl its looking for libffi.so.6 but libffi.so.5 its installed instead.
running revdep-rebuild now. |
|
Back to top |
|
|
iplayfast l33t
Joined: 08 Jul 2002 Posts: 642 Location: Cambridge On,CA
|
Posted: Tue Dec 06, 2011 7:57 pm Post subject: |
|
|
I've got into this situation, with over 500 files to update, and libfii.so.6 not available. After reading this it looks like There was a libfii.so.6 but for some reason the new version is libfii.so.5 messing all sorts of stuff up.
My quick an dirty solution was Code: | ln -s /usr/lib/libfii.so.5 /usr/lib/libfii.so.6 |
So that any files needing the files were able to build.
revdep-build just wasn't cutting it. This worked for me. |
|
Back to top |
|
|
sno35 Guru
Joined: 15 May 2004 Posts: 334 Location: Paris, France
|
Posted: Mon Dec 10, 2012 7:16 am Post subject: |
|
|
Re-emerge-ing gobject-introspection sufficed for my libffi.6 / .4 mismatch. |
|
Back to top |
|
|
|