Re: pkglibdir versus libdir?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pkglibdir versus libdir?
Date: 2003-07-31 14:14:09
Message-ID: 1258.1059660849@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> Peter, I'm a little confused about the difference between the libdir and
>> pkglibdir settings created by configure. What's supposed to go where?

> libdir is for build-time linkable libraries, anything that you might want
> to pass as -lxxx. So typical locations are /usr/lib, /usr/local/lib, or
> /usr/local/pgsql/lib. pkglibdir is for dynamically loadable
> libraries,

Okay, so anything meant to be loaded by the backend goes in pkglibdir?

>> I got a complaint from a Red Hat person that the regression tests failed
>> on a 64-bit machine. Some investigation revealed that the problem was
>> that plpgsql.so got installed into $libdir while pg_regress.sh expected
>> to find it in $pkglibdir.

> Umm... from src/pl/plpgsql/src/Makefile:

Actually, further investigation revealed that there is brain damage in the
rpm patches: some places have been hacked to have hard-wired paths.
As soon as $libdir is not /usr/lib, the rpm patches roll over and die.
We mistakenly blamed this on a libdir-vs-pkglibdir discrepancy, until we
noticed what was actually getting executed ...

Thanks for the response.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-07-31 14:14:59 Re: how to dump all tables with pg_dump ?
Previous Message Tom Lane 2003-07-31 13:58:31 Re: version mismatch message