Thus spake D'Arcy J.M. Cain
> After upgrading my system to -current (on a new drive so no baggage left
> from the old system) I ran into a problem with PostgreSQL libraries.
> For some reason we put the PostgreSQL libraries under ${LOCALBASE}/pgsql
> lib directory instead of the ${LOCALBASE} one.  This causes problems
> with PyGreSQL (and perhaps other stuff I haven't tried) which uses the
> libraries dynamically.  At run time it fails to find this because the
> loader doesn't look there.  I can fix this in PyGreSQL I suppose by
> having the package compile in the location but wouldn't it be better
> to put the PostgreSQL libraries in LOCALBASE with the rest of them so
> that other programs of this nature don't have to repeat this?

No answer so how about I make the trivial change to the package so that
it builds and runs under ELF?  It just needs the following change to
Setup.in under files.

<_pg pgmodule.c -I@PGPREFIX@/include -L@PGPREFIX@/lib -lpq -lcrypt -DNO_DIRECT
>_pg pgmodule.c -I@PGPREFIX@/include -Wl,-R@PGPREFIX@/lib -L@PGPREFIX@/lib -lpq -lcrypt -DNO_DIRECT

My understanding is that this will not affect a.out systems.  Unless I hear
something to the contrary I'll go ahead an make the change tomorrow.

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.