On Dec 26, 2012, at 11:58, Robert Muir wrote:
> On Wed, Dec 26, 2012 at 11:14 AM, Andi Vajda wrote:
>>
>> Very strange. Why would it go out to pypi to install unrelated packages ?
>> Odd. Did you run just 'make' first before running 'make test' ? (my
>> workflow).
>>
>
> I just tried make,
On Wed, Dec 26, 2012 at 11:14 AM, Andi Vajda wrote:
>
> Very strange. Why would it go out to pypi to install unrelated packages ?
> Odd. Did you run just 'make' first before running 'make test' ? (my workflow).
>
I just tried make, followed by make test, and it worked fine. So I
think i must have
On Dec 26, 2012, at 10:50, Robert Muir wrote:
> On OS X, i had to run 'make test' twice. The first time, i got a strange
> error:
>
> Installed
> /Users/rmuir/pylucene/pylucene-3.6.2-1/build/test/lucene-3.6.2-py2.7-macosx-10.7-x86_64.egg
> Processing dependencies for lucene==3.6.2
> Searching
On OS X, i had to run 'make test' twice. The first time, i got a strange error:
Installed
/Users/rmuir/pylucene/pylucene-3.6.2-1/build/test/lucene-3.6.2-py2.7-macosx-10.7-x86_64.egg
Processing dependencies for lucene==3.6.2
Searching for lucene==3.6.2
Reading http://pypi.python.org/simple/lucene/
i installed java7 on my os X... with the following build patch
pylucene seems to work fine (tests pass etc).
I think java7 is just pickier about -source/-target both being set for
jcc. And the extensions should use the same explicit source/target (or
the build can hit classfile version problems).
