| 1 |
Donnie Berkholz wrote: |
| 2 |
|
| 3 |
> On 14:52 Thu 05 Jun , Samuli Suominen wrote: |
| 4 |
>> # Samuli Suominen <drac@g.o> (05 Jun 2008) |
| 5 |
>> # Masked for removal in ~30 days by treecleaners. |
| 6 |
>> # Replaced by USE libffi in sys-devel/gcc. Bug 163724. |
| 7 |
>> dev-libs/libffi |
| 8 |
>> dev-lang/squeak |
| 9 |
>> x11-libs/gtk-server |
| 10 |
> |
| 11 |
> The latest version of g-wrap (1.9.11) requires the external libffi |
| 12 |
> released a month or two ago, because it looks for the pkgconfig file |
| 13 |
> installed by that and not gcc: |
| 14 |
> |
| 15 |
> - libffi is no longer distributed with g-wrap, as it is available |
| 16 |
> as a stand-alone package now (instead of being burried in the |
| 17 |
> GCC sources). |
| 18 |
> |
| 19 |
> Thoughts? |
| 20 |
|
| 21 |
I'd vote for an external libffi as well since python currently has to use |
| 22 |
it's bundled version of it (statically linking against it). |
| 23 |
Using libffi provided by gcc (and linking dynamically) is no option yet |
| 24 |
since portage doesn't protect the user from destroying his system by |
| 25 |
re-emerging gcc without gcj or libffi USE flags (rev-dep check and |
| 26 |
USE-based deps would be needed). |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@l.g.o mailing list |
Archives