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