lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andi Vajda <>
Subject Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Date Thu, 09 Dec 2010 22:24:47 GMT

On Wed, 8 Dec 2010, Andi Vajda wrote:

> On Wed, 8 Dec 2010, Bill Janssen wrote:
>> Andi Vajda <> wrote:
>>> Yes, two things made me do this:
>>>   1. Bill Janssen said on this list that an Apple developer he talked to
>>>      said that the /Developer tree is the correct one to use.
>> I asked again, and got this answer.  Looks like I was (wrong? talking
>> about a pre-release version of Snow Leopard?); Mike says to just use
>> /System/Library/Frameworks/JavaVM.framework/Headers, and explains why
>> that doesn't always work, and that they're aware of the problem.
>> So let's just hardcode that path into the file for "darwin".
> That would be the safer thing to do at this point, yes.

I finally opted to stay with the current setting under /Developer since, if 
there is one version that should work out of the box, it should be the 
latest OS/Java combination. Once Apple changes it again, if they do, I can 
change it back as well so that more setups work again out of the box.


> I wasn't able to build on 10.5 yesterday (my old G4 powerbook needs some 
> refreshing first [1]). Once I confirm 10.5 presents no problems, I'm probably 
> going to revert the change and prepare new release artifacts and 
> call for another vote.
> Andi..
> [1] bitrot story:
>  - the svn I have installed there doesn't support the externals format used
>  - updating svn via MacPorts requires a MacPorts update first
>  - updating MacPorts implies a dev tools update (since it complains about
>    Xcode 3.0 causing "problems")
>  - installing the 3.2.2 devtools on my 10.5.8 G4 powerbook crashes the
>, consistently, while "looking for installation volumes"
>  - downloading the 3.2.5 devtools took 3 hrs (3.52GB download, I was not
>    able to find a Xcode-only .dmg, only Xcode+iPhone SDK, iPhone part which
>    is not even supported on 10.5), download completed overnight
>  - no time to continue this until tonight again
>> Bill
>> Subject: Re: how to locate an installed JDK?
>> From: Mike Swingler <>
>> Date: Wed, 8 Dec 2010 07:13:59 PST
>> Cc: java-dev <>
>> On Dec 7, 2010, at 7:08 PM, Bill Janssen wrote:
>>> Now that we have /usr/libexec/java_home, is there a standard way to
>>> locate a JDK, with tools like "javac" and "jar" and header files like
>>> "jni.h"?
>>> The PyLucene project installs a tool called "JCC", which wraps a jar
>>> file as a Python module, but to build JCC, it has to find a Java JDK
>>> with header files.  Is there a standard way of doing that yet?
>> To find a $JAVA_HOME for the purposes of using the command line tools,
>> please use /usr/libexec/java_home. The man page for "java_home"
>> enumerates all of it's options.
>> As for headers, always use 
>> /System/Library/Frameworks/JavaVM.framework/Headers.
>> It may be necessary to install the "Java for Mac OS X 10.6 Update 3
>> Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
>> Package" from <> under the "Java" section, to
>> ensure the native headers are present in the JavaVM.framework. We are
>> aware that this has caused some inconvenience for otherwise native
>> projects that make use of the JNI API, and we are leaning towards just
>> shipping the headers in the regular customer software update package.
>> Regards,
>> Mike Swingler
>> Java Engineering
>> Apple Inc.

View raw message