Hi, I usually get a bunch of compiler warnings during the build (mostly related to implicit type conversion) so I don't pay much attention on it - unless build or test fails…
Just checked the output of my last Mac build and could in deed find similar issues as reported by Mike. See log here: https://dl.dropbox.com/u/4384120/macosbuildjcc215pylucene362log.txt 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 -- Am 03.01.2013 um 01:58 schrieb Andi Vajda <va...@apache.org>: > > On Wed, 2 Jan 2013, Michael McCandless wrote: > >> Sorry for the delay here ... was out on vacation. Happy new year! > > Happy new year to you too ! > >> I tested on OS X 10.8.2, and was able to install & run my usual smoke >> test (index & search first 100K Wikipedia docs). >> >> But I hit a few strange things ... first, lots of compilation warnings >> when compiling jcc and pylucene, eg: >> >> In file included from build/_lucene/JArray.cpp:21: >> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/JArray.h:104:102: >> warning: implicit conversion loses integer precision: 'Py_ssize_t' >> (aka 'long') to 'jsize' >> (aka 'int') [-Wshorten-64-to-32] >> JArray<jobject>(jclass cls, Py_ssize_t n) : >> java::lang::Object(env->get_vm_env()->NewObjectArray(n, cls, NULL)) { >> ~~~ >> ^ > > This could be a mismatch between 32-bit Python and 64-bit Java ? > I don't know for sure, I've not seen this error but it's clearly complaining > about losing 32 out of 64 bits somewhere. > >> and: >> >> #define PySequence_Length PySequence_Size >> ^ >> build/_lucene/__wrap05__.cpp:294:16: warning: implicit conversion >> loses integer precision: 'Py_ssize_t' (aka 'long') to 'unsigned int' >> [-Wshorten-64-to-32] >> if (!parseArgs(args, "s", &a0)) >> ^~~~~~~~~~~~~~~~~~~~~~~~~ >> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/functions.h:63:43: >> note: expanded from macro 'parseArgs' >> >> They are all warnings and the compilation succeeded ... >> >> This could easily be user error ... I didn't change anything in jcc's >> setup.py ... just ran it as was. And I just uncommented the top "Mac >> OS X 10.6" section in the Makefile ... Python is 2.7.2, java is >> 1.6.0_35. >> >> The second strange problem I hit was during "make install" in >> pylucene: it installed lots of stuff but then hit this odd error: > > Did you run 'make' first, then 'make install' or just 'make install' straight > from scratch ? > > Both of these issues could be because you're using the stock Python 2.7 on > Mac OS X 10.8.2 ? I've got a custom install for each and every PyLucene > branch I maintain and these seem new enough to be correlated to 10.8.2 ? (I > just upgraded to that myself two weeks ago). > > Thanks for checking ! > > Andi.. > >> >> Adding lucene 3.6.2 to easy-install.pth file >> >> Installed >> /Library/Python/2.7/site-packages/lucene-3.6.2-py2.7-macosx-10.8-x86_64.egg >> Processing dependencies for lucene==3.6.2 >> Searching for lucene==3.6.2 >> Reading http://pypi.python.org/simple/lucene/ >> Couldn't find index page for 'lucene' (maybe misspelled?) >> Scanning index of all packages (this may take a while) >> Reading http://pypi.python.org/simple/ >> No local packages or download links found for lucene==3.6.2 >> error: Could not find suitable distribution for >> Requirement.parse('lucene==3.6.2') >> make: *** [install] Error 1 >> >> Looks like this is the same thing Rob hit during "make test" ... but >> my "make test" succeeded (after I hit the issue during "make >> install"). >> >> I was then able to run my smoke test and confirmed it was Lucene 3.6.2 >> under the hood ... >> >> But net/net +1 to release: I didn't hit any showstoppers... >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> On Wed, Jan 2, 2013 at 5:21 AM, Thomas Koch <k...@orbiteam.de> wrote: >>> Update: I was also able to build JCC2.15/PyLucene3.6.2 on Win7(32 bit) with >>> Python 2.7.2, Java 1.6 and MSVC9.0 >>> >>> >>> Regards, >>> Thomas >>> >>> -----Ursprüngliche Nachricht----- >>> Von: Thomas Koch [mailto:k...@orbiteam.de] >>> Gesendet: Sonntag, 30. Dezember 2012 15:22 >>> An: pylucene developers >>> Betreff: Re: [VOTE] Release PyLucene 3.6.2 >>> >>> Hi, >>> build succeeded on MacOS 10.8.2 with Python 2.7.2 and java 1.6.0_37. (=> +1) >>> >>> I'm currently at home (xmas break) and don't have access to my >>> Windows-build-environment, but can test on Win7 next week too. >>> >>> regards >>> Thomas >>> -- >>> Am 26.12.2012 um 03:56 schrieb Andi Vajda <va...@apache.org>: >>> >>>> >>>> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene >>> 3.6.2 is ready. >>>> >>>> A release candidate is available from: >>>> http://people.apache.org/~vajda/staging_area/ >>>> >>>> A list of changes in this release can be seen at: >>>> >>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_6/CHANGE >>> S >>>> >>>> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts: >>>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES >>>> >>>> A list of Lucene Java changes can be seen at: >>>> >>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHA >>> NGES.txt >>>> >>>> Please vote to release these artifacts as PyLucene 3.6.2-1. >>>> >>>> Thanks ! >>>> >>>> Andi.. >>>> >>>> ps: the KEYS file for PyLucene release signing is at: >>>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS >>>> http://people.apache.org/~vajda/staging_area/KEYS >>>> >>>> pps: here is my +1 >>> >>>
