From: books at ejurka.com (Kris Jurka)
Date: Wed, 18 Mar 2009 17:08:58 -0700
Subject: [Pljava-dev] Build Errors while building PL/Java 1.4.0
 on	Solaris 10
In-Reply-To: 
 <6ECF8F2E89FB354F9D3E26F7A398842BCCDBAC@CORPUSMX100A.corp.emc.com>
References: <6ECF8F2E89FB354F9D3E26F7A398842BCCDAA0@CORPUSMX100A.corp.emc.com>
	<49C167BA.1050005@ejurka.com>
	<6ECF8F2E89FB354F9D3E26F7A398842BCCDBAC@CORPUSMX100A.corp.emc.com>
Message-ID: <49C18D1A.3000705@ejurka.com>

Prabhakara_Janardhan at emc.com wrote:
> 
> Yes! The server was built elsewhere... Are you saying that PL/Java
> should always be built on the same server as the server itself? That is
> kind of a severe restriction, esp. when we have pg_config etc - to tell
> us all the flags that were used and essentially that should be all that
> should be known. Anyhow, I was quite convinced that the way I built it
> was fine - was just wondering why I got that error in the first place.
> 

So your situation is:  postgresql was built on server A which does not 
have unsetenv and must use the postgresql provided built in version. 
pljava was built on Server B which does have unsetenv and therefore 
chokes when trying to include the postgresql built in version.  I'm not 
saying that you must build all the software on the server that it will 
be deployed upon, but you're asking for trouble if they aren't the same. 
  Consider what would happen if you did this in reverse, building 
postgresql on Server B and deploying it on Server A, it wouldn't even 
run because Server A doesn't have unsetenv and postgresql got built 
without its internal version because it was available on Server B.

Kris Jurka