On Apr 22, 2006, at 4:06 PM, Daniel Lord wrote:
...
> cc -arch ppc -arch i386 -Wl,-syslibroot,/Developer/SDKs/
> MacOSX10.4u.sdk -o static static.o -L. -lanswer
...
> /usr/bin/ld: for architecture ppc
> /usr/bin/ld: warning static.o cputype (7, architecture i386) does
> not match cputype (18) for specified -arch flag: ppc (file not loaded)
> rch flag: ppc (can't load from it)
> /usr/bin/ld: Undefined symbols:
> _main
> collect2: ld returned 1 exit status
> lipo: can't open input file: /var/tmp//ccEO7pnk.out (No such file
> or directory)
> make: *** [static] Error 1
>
>
> Then poking around the docs and "Advanced OSX Programming", I found
> something to try:
>
> LDFLAGS = -arch ppc -arch i386 -Wl,-syslibroot,/Developer/SDKs/
> MacOSX10.4u.sdk
>
> And that did it. Try it an let me know if that solves your
> problem...more later after I figure out the details
Not sure I understand -- you do seem to have those flags in the cc
command I left quoted above. Also, building with "python
setup.py" (as always recommended for compiling and linking Python
extensions) already specifies those flags, so that exporting that
LDFLAGS causes an error due to the repetition...:
gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g
-bundle -undefined dynamic_lookup -arch ppc -arch i386 -Wl,-
syslibroot,/Developer/SDKs/MacOSX10.4u.sdk build/temp.macosx-10.4-
fat-2.4/src/gmpy.o -L/usr/local/lib -lgmp -o build/lib.macosx-10.4-
fat-2.4/gmpy.so
/usr/bin/ld: -syslibroot: multiply specified
collect2: ld returned 1 exit status
/usr/bin/ld: -syslibroot: multiply specified
collect2: ld returned 1 exit status
etc. Maybe I misunderstand what you're suggesting...?
Thanks,
Alex
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
