|
Graham Dumpleton
grahamd at dscpl.com.au
Fri Jan 12 05:06:40 EST 2007
BTW, I know you want to use Python 2.4, but can you go back and actually try the Python 2.3.5 supplied with the operating system as standard instead to see if that works. Graham On 12/01/2007, at 1:50 PM, Graham Dumpleton wrote: > michael starke wrote .. >> I'm confused, either i'm making some stupid mistake all the time or >> it's still not working. >> I removed the 3 arguments one by one and still, the built fails. >> Damn, is there a way to get the mod built on another machine and then >> just load up the installtion to the macbook, hoping that it works? > > Are you doing a: > > make clean > > between build attempts when changing the makefile? > > Can you run: > > gcc -v > > again so can see what version number it is now saying? > > Graham > > >> On 11.01.2007, at 22:07, Graham Dumpleton wrote: >> >>> >>> On 12/01/2007, at 2:48 AM, michael starke wrote: >>> >>>> Even the routines make mistakes, makes them look more human. >>>> >>>> I did what you suggested, the line in my makefile (after >>>> configure, i told you, am new to this =) looks like this: >>>> >>>> LDFLAGS= -Wl,-framework,Python -u _PyMac_Error $ >>>> (PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK) - >>>> arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g >>>> >>>> I changed it to >>>> >>>> LDFLAGS= -Wl,-framework,Python -u _PyMac_Error -arch i386 -arch >>>> ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g >>> >>> Try taking out: >>> >>> -arch ppc >>> >>> and if still not working, also take out: >>> >>> -arch i386 >>> >>> You could even drop the: >>> >>> -isysroot /Developer/SDKs/MacOSX10.4u.sdk >>> >>> which I have never seen before and may be screwing up libtool. >>> >>> Graham >>>
|