| 1 |
On 05-10-2009 11:56:11 +0100, Alan Hourihane wrote: |
| 2 |
> On Mon, 2009-10-05 at 11:45 +0200, Fabian Groffen wrote: |
| 3 |
> > On 04-10-2009 10:02:07 +0200, Fabian Groffen wrote: |
| 4 |
> > > > What happened ? |
| 5 |
> > > |
| 6 |
> > > Good questions. I merged this change from gx86 already with the |
| 7 |
> > > comment that this would probably break (again ...). Also in the ebuild, |
| 8 |
> > > internal libffi is removed conditional now, but that would mean |
| 9 |
> > > virtual/libffi would have to have keywords for ~mips and ~m68k now. |
| 10 |
> > > It does not. Seems bugzie is down at the moment, so I can't check if |
| 11 |
> > > there are already bugs for this issue. |
| 12 |
> > |
| 13 |
> > ~m68k and ~mips keywords were just recklessly dropped from the ebuild. |
| 14 |
> > |
| 15 |
> > Given that python compiled fine at some point in the past, does Python's |
| 16 |
> > internal libffi compile on m68k-mint, or did it just skip libffi |
| 17 |
> > dependant modules? |
| 18 |
> |
| 19 |
> python-2.6.2-r2 compiled just fine without libffi when the ebuild had |
| 20 |
> the ~m68k-mint keyword on virtual/libffi. |
| 21 |
|
| 22 |
yeah, but back then it didn't rm -Rf internal/libffi |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Fabian Groffen |
| 27 |
Gentoo on a different level |
Archives