On Wednesday 04/16/08 @ 6:36 am MDT, I received this from Andrew 
Sullivan <ajs at crankycanuck.ca>:
> On Tue, Apr 15, 2008 at 08:37:49PM -0600, Ed L. wrote:
> > Your question makes me wonder if the gcc check is necessary
> > since my old Pg 8.1.2 configure.log shows that, using the
> > same compiler+flags, there's no obvious check for gcc like
> > the one above (and it builds correctly):
>
> Part of the reason I'm bothered is because of the opacity of
> the error you get.  You seem to be getting an error with no
> reason.  It's gonna be pretty hard to troubleshoot it without
> access to an HP-UX system.

Unfortunately I can't help you with access.  But I can try 
suggestions.  Is there a way to turn up the debug volume on make 
ala 'sh -v script.sh'?

Building with gcc (and CFLAGS="-mlp64" LDFLAGS="-mlp64) results 
in the exact same error output.  If I built pg with ANSI C 
compiler using "+DD64", is there any dependency requiring me to 
build slony with the same compiler since it links with pg's 
libs?  Or should their end results be compatible due to same 
architecture?

Other ideas to try?

Ed