On Apr 10, 2008, at 0:04, "benny daon" <[EMAIL PROTECTED]> wrote:
Hi all,
I can't find a way to make my my Intel 10.4 Mac compile PyLucene
only for i386. So far I've tried:
- make CFLAGS="-arch i386" LDFLAGS="-arch i386"
- sudo env ARCHFLAGS="-arch i386"
but make always ends with:
g++ -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -
g -bundle -undefined dynamic_lookup build/temp.macosx-10.3-fat-2.5/
build/_lucene/__init__.o build/temp.macosx-10.3-fat-2.5/build/
_lucene/__wrap__.o build/temp.macosx-10.3-fat-2.5/build/_lucene/
functions.o build/temp.macosx-10.3-fat-2.5/build/_lucene/jcc.o build/
temp.macosx-10.3-fat-2.5/build/_lucene/JCCEnv.o build/
temp.macosx-10.3-fat-2.5/build/_lucene/JObject.o build/
temp.macosx-10.3-fat-2.5/build/_lucene/lucene.o build/
temp.macosx-10.3-fat-2.5/build/_lucene/types.o -o build/
lib.macosx-10.3-fat-2.5/lucene/_lucene.so -framework JavaVM -Wl,-S
/usr/bin/ld: for architecture ppc
/usr/bin/ld: warning build/temp.macosx-10.3-fat-2.5/build/_lucene/
__init__.o cputype (7, architecture i386) does not match cputype
(18) for specified -arch flag: ppc (file not loaded)
The compile flags used by distutils/setuptools to build JCC and
PyLucene come from Python itself. It Python was configured to be built
as a universal build then extensions will also be built that way. I
don't know how to effectively override that besides rebuilding Python
with the desired config.
Note that the error you're getting can be ignored. You still have a
usable executable and can proceed.
Andi..
...
Thanks,
Benny
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
