[pylucene-dev] pylucene/jcc compilation issues

[Phil Christensen]

On Oct 25, 2007, at 5:12 AM, Henrik Dittmann wrote:
> I'm new to the list as well as (Py)Lucene. A couple of days ago I have
> installed PyLucene with JCC, so I might bother you with a few  
> questions
> in days to come..
>
> Phil Christensen schrieb am 25.10.2007 6:10 Uhr:
>> On Oct 24, 2007, at 9:39 PM, Andi Vajda wrote:
>>> Could it be that sudoing changes the environment you're in for some
>>> reason, causing LD_LIBRARY_PATH to no longer be correct ? (unsure
>>> myself).
>>
>> I suspected this as well, and tried it as root, same result. Sorry I
>> didn't remove those variables from my example.
>
> When compiling (on Ubuntu 7.10, with Java 1.6 and Python 2.5.1) I had
> the same error as Phil initially. For me it went away when I became  
> root
> prior to setting LD_LIBRARY_PATH, something like:
>
> $ export LD_LIBRARY_PATH=...
> $ make
> $ sudo bash
> $ (as root) export LD_LIBRARY_PATH=...
> $ (as root) make install
> $ exit

I feel really stupid, but actually becoming root before doing this  
fixed my problem. I *swear* I tried this before, but I guess I didn't.

> Hope I am not hijacking your thread here, Phil, but a question that
> seems closely related: Am I right in understanding that you have to  
> keep
> the LD_LIBRARY_PATH around for running PyLucene with JCC? If I  
> don't put
> it somewhere in my .profile or .bashrc, I get the same error about  
> being
> unable to open libjava.so whenever I import PyLucene.

This is the behavior I'm seeing as well. I don't understand why this  
would happen, why would this variable be needed after compilation?

I'm certainly not complaining, but I feel like having a dependency on  
LD_LIBRARY_PATH could bring up various issues in the future. This  
page I found explains it pretty well, although with a slightly snarky  
attitude ;-):

     http://linuxmafia.com/faq/Admin/ld-lib-path.html

Anyways, thanks to everyone for the help getting this far.

-phil