On Jan 3, 2013, at 2:18, "Thomas Koch" <k...@orbiteam.de> wrote:
> Maybe I should add that both java and python are universal binary files for > 32/64 bit : > > ios:~ koch$ file /usr/bin/java > /usr/bin/java: Mach-O universal binary with 2 architectures > /usr/bin/java (for architecture x86_64): Mach-O 64-bit executable > x86_64 > /usr/bin/java (for architecture i386): Mach-O executable i386 > > ios:~ koch$ file /usr/bin/python > /usr/bin/python: Mach-O universal binary with 2 architectures > /usr/bin/python (for architecture i386): Mach-O executable i386 > /usr/bin/python (for architecture x86_64): Mach-O 64-bit executable > x86_64 > > It seems to me that JCC is also build for both architecture because of the > flags -arch i386 AND -arch x86_64. > Maybe the warning relates to the 32bit binaries? Just guessing - don't > really know how this universal binary compile magic really works ,-( When building PyLucene on my mac, I only build the 64-bit version by specifying -arch x86_64, skipping the 32-bit version. It cuts build time (and size) in half. Andi.. > > However Apple Docs say one should take care of theses warnings: > > --%<-- > -Wshorten-64-to-32 > > This flag is like -Wconversion, but is specific to 64-bit data types. > This flag causes GCC to issue a warning whenever a value is implicitly > converted (truncated) from a 64-bit type to a 32-bit type. You should fix > any warnings generated by this flag, as they are likely to be bugs. > --%<-- > Found here: > https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/64b > itPorting/building/building.html > > > regards > Thomas > >> -----Ursprüngliche Nachricht----- >> Von: Thomas Koch [mailto:k...@orbiteam.de] >> Gesendet: Donnerstag, 3. Januar 2013 09:54 >> An: pylucene developers >> Betreff: Re: [VOTE] Release PyLucene 3.6.2 >> ... >> I'm on 10.8.2 too with builtin python 2.7.2. I used the makefile snippet > for >> Mac OS X 10.6 (for 64-bit and 32-bit Python): >> >> PREFIX_PYTHON=/usr >> ANT=ant >> PYTHON=$(PREFIX_PYTHON)/bin/python >> JCC=$(PYTHON) -m jcc.__main__ --shared --arch x86_64 --arch i386 >> NUM_FILES=4 >> >> As said: jcc and pylucene both build and run fine… >> >> >> regards, >> Thomas > > >
