Bug 200679 – dev-libs/g-wrap and gcc 4.2.2 both install a libffi.so.4 leading to crashes

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Marc Geerlings 2007-11-28 18:55:06 UTC]

I filed a bug more then a month ago (bug #198925), describing crashes in Totem and Rhythmbox (and later Gedit). In the last hour there was a suggesting of unmerging g-wrap and then do a revdep-rebuild (see bug #198925) It seems that both gcc 4.2.2 and g-wrap install a libffi.so.4, unmerging g-wrap and do a revdep-rebuild will not reinstall g-wrap but link all the applications to the gcc-4.2.2 libffi.so.4

Reproducible: Always

[Comment 1 Jakub Moc (RETIRED) 2007-11-28 18:55:43 UTC]

Has nothing to do w/ Gnome.

[Comment 2 Marijn Schouten (RETIRED) 2007-11-28 19:01:48 UTC]

I was only installing libffi bundled with g-wrap because of bug 163724. I don't think gcc ALWAYS installs libffi though. What are your use flags for it?

[Comment 3 Marc Geerlings 2007-11-28 19:20:24 UTC]

Created attachment 137264 [details]
My emerge --info

Oh yeah, then discard this bug on semantics, if it has nothing to do with Gnome...
I don't care, 

I´ve a very frustating month behind me with a barely working system because of this, all of them gtk+/gnome applications. My system has made hours compiling and recompiling the whole system to resolve it. I'm a little short tempered now!

Here is my emerge --info

[Comment 4 Rémi Cardona (RETIRED) 2007-11-28 19:34:57 UTC]

*** Bug 200681 has been marked as a duplicate of this bug. ***

[Comment 5 SpanKY 2007-11-29 01:26:55 UTC]

libffi is the toolchain domain, certainly not some random scheme package

[Comment 6 Jakub Moc (RETIRED) 2008-02-28 10:17:32 UTC]

scheme, please remove the bundled libffi from the g-wrap ebuilds, it totally doesn't belong there. If something needs it, then it should check for gcc built w/ USE=libffi now that Bug 199850 is fixed.

[Comment 7 Samuli Suominen (RETIRED) 2008-06-05 12:01:03 UTC]

ACK

[Comment 8 Gilles Dartiguelongue (RETIRED) 2009-05-07 09:39:16 UTC]

last stable still provides custom libffi and although lines doing it are commented in lastest ~arch ebuild, there is no dependency on gcc provided libffi or split libffi package. Please finish this off.

[Comment 9 Samuli Suominen (RETIRED) 2009-06-01 07:40:18 UTC]

Please use virtual/libffi, it's at a KEYWORDREQ state in bug 272046.

[Comment 10 Samuli Suominen (RETIRED) 2009-06-04 18:22:42 UTC]

Adding QA.

g-wrap-1.9.11.ebuild:KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
g-wrap-1.9.6-r3.ebuild:KEYWORDS="alpha amd64 ppc sparc x86"
g-wrap-1.9.8.ebuild:KEYWORDS="~alpha ~amd64 ~ppc ~sparc ~x86"
g-wrap-1.9.9.ebuild:KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"

Which one is the fixed version? Others need to be removed. Any of them? Should we package.mask g-wrap and everything that deps on it for removal.. ?

[Comment 11 Samuli Suominen (RETIRED) 2009-06-04 18:24:39 UTC]

Request the fixed g-wrap which..

- doesn't ship a libffi.
- doesn't depend on USE libffi from sys-devel/gcc
- deps on virtual/libffi

to stable now.

[Comment 12 Samuli Suominen (RETIRED) 2009-06-04 18:43:52 UTC]

Seems to be fixed in g-wrap-1.9.11.. requesting it in stable on another bug to remove all older versions.