Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Mon, 2009-10-05 at 11:45 +0200, Fabian Groffen wrote:
> On 04-10-2009 10:02:07 +0200, Fabian Groffen wrote:
> > > What happened ?
> >
> > Good questions. I merged this change from gx86 already with the
> > comment that this would probably break (again ...). Also in the ebuild,
> > internal libffi is removed conditional now, but that would mean
> > virtual/libffi would have to have keywords for ~mips and ~m68k now.
> > It does not. Seems bugzie is down at the moment, so I can't check if
> > there are already bugs for this issue.
>
> ~m68k and ~mips keywords were just recklessly dropped from the ebuild.
>
> Given that python compiled fine at some point in the past, does Python's
> internal libffi compile on m68k-mint, or did it just skip libffi
> dependant modules?
python-2.6.2-r2 compiled just fine without libffi when the ebuild had
the ~m68k-mint keyword on virtual/libffi.
Alan.
|
|
