Re: $libdir and 8.0

From: Paul Ramsey <pramsey(at)refractions(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: $libdir and 8.0
Date: 2004-08-19 05:00:04
Message-ID: 412433D4.9080902@refractions.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sounds like we are getting close. From strace:

stat64("/home/pramsey/pgtest/8.0/bin/lib/postgresql/plpgsql",
0xbfffe480) = -1 ENOENT (No such file or directory)
stat64("/home/pramsey/pgtest/8.0/bin/lib/postgresql/plpgsql.so",
0xbfffe480) = -1 ENOENT (No such file or directory)
stat64("$libdir/plpgsql", 0xbfffe540) = -1 ENOENT (No such file or
directory)

I started the database from "/home/pramsey/pgtest/8.0/bin" using
"./pg_ctl start -D /home/pramsey/pgtest/8.0/data"

Judging from the behavior I have posted to the list of "pg_config
--pkglibdir", if I started it from any *other* location at all then
things would have worked.

Paul

Tom Lane wrote:
> Paul Ramsey <pramsey(at)refractions(dot)net> writes:
>
>>... It is the actual binaries that seem to not know
>>where $libdir is supposed to be.
>
>
> Where do they think it is?
>
> A useful way to check would be to strace the backend while you're
> executing "createlang" or another command that tries to load a
> dynamic library. The file names that it tries to stat() would be
> good evidence.
>
> Also, how are you starting the postmaster? I believe that current
> sources will try to locate $libdir via a relative path from where
> the postmaster executable is. We've fixed some bugs in that area
> recently, but maybe there are more.
>
> regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Ramsey 2004-08-19 05:03:53 Re: $libdir and 8.0
Previous Message Paul Ramsey 2004-08-19 04:52:33 Re: $libdir and 8.0