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