On May 12, 2013, at 21:04, Barry Wark <ba...@physion.us> wrote: > Hi all, > > I'm new to the pylucene-dev list, so please forgive me if I'm stepping out of > line in the voting process. > > We're using sucesfully JCC 2.15 to generate a wrapper for our Java API. JCC > 2.16 from SVN HEAD produces the following error (output log attached) when > using the new --use_full_names option. Python 2.7, OS X 10.8: > > build/_ovation/com/__init__.cpp:15:14: error: use of undeclared identifier > 'getJavaModule' > module = getJavaModule(module, "", "com"); > ^ > build/_ovation/com/__init__.cpp:22:14: error: use of undeclared identifier > 'getJavaModule' > module = getJavaModule(module, "", "com");
You might be mixing in headers from an old version here... Andi.. > ^ > 2 errors generated. > error: command 'clang' failed with exit status 1 > > > The generated _ovation/__init__.cpp and _ovation/com/__init__.cpp are also > attached. > > Cheers, > Barry > > > On Mon, May 6, 2013 at 8:27 PM, Andi Vajda <va...@apache.org> wrote: >> >> It looks like the time has finally come for a PyLucene 4.x release ! >> >> The PyLucene 4.3.0-1 release tracking the recent release of Apache Lucene >> 4.3.0 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_4_3/CHANGES >> >> PyLucene 4.3.0 is built with JCC 2.16 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_4_3_0/lucene/CHANGES.txt >> >> Please vote to release these artifacts as PyLucene 4.3.0-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 > > <jcc_2.16_osx_10.8_py2.7.out.txt> > <__init__.cpp> > <__init__.cpp>
