From: thhal at mailblocks.com (Thomas Hallgren)
Date: Wed, 25 May 2005 20:01:48 +0200
Subject: [Pljava-dev] libjvm.so error
In-Reply-To: <4294955E.1010107@bonbon.net>
References: <200505242238.j4OMbxEJ015903@bigmac.hydroblaster.com>
	<42940D38.9040905@mailblocks.com>
	<thhal-0uqVvA4H0zTYEV3dMb/kpXoJTFlksdP@mailblocks.com>
	<thhal-0uqVvA4P0zTYK+D9Mr2S2sORi1zW1fD@mailblocks.com>
	<4294890D.3040007@bonbon.net>
	<4294955E.1010107@bonbon.net> <4294BD8C.80306@mailblocks.com>
	<thhal-0DlZwA//5zTYomPYevkemj79tlagH9n@mailblocks.com>
Message-ID: <thhal-0D1ZwAwH6zTYddn4rnIQkZOaPExVd7M@mailblocks.com>

Eric E wrote:

> Hi all,
> Well, I'm guessing that lack of LD_LIBRARY_PATH is coming back to bite 
> me again...  I went to run the examples, and got this in the log (I 
> was impressed at how Postgres handled the crash :)
>
>
> 2005-05-25 10:57:48 LOG:  Error occurred during initialization of VM
> 2005-05-25 10:57:48 LOG:  Unable to load native library
> 2005-05-25 10:57:48 LOG:  : libverify.so: cannot open shared object 
> file: No such file or directory
>
> and of course, libverify.so  is in /usr/lib/jvm/java/jre/lib/i386 ...
>
> So I guess I'm back to my previous question - how do I make the 
> postmaster aware of LD_LIBRARY_PATH?

Exporting it just before the command that starts the postmaster 
executable sure does it for me. I don't know any other way.

Regards,
Thomas Hallgren