Skip site navigation (1) Skip section navigation (2)

Re: BUG #1072: "$libdir/ascii_and_mic": No such file or directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas Borg Salling" <tbs(at)navicon(dot)dk>
Cc: "'PostgreSQL Bugs List'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #1072: "$libdir/ascii_and_mic": No such file or directory
Date: 2004-02-02 18:44:15
Message-ID: 19678.1075747455@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Thomas Borg Salling" <tbs(at)navicon(dot)dk> writes:
> I replaced "$libdir" with "/opt/postgres-7.4.1/lib" throughout
> /opt/postgres-7.4.1/share/conversion_create.sql -- then initdb succeeded!

Well, that proves the shared library wasn't broken, but it leaves us
no wiser about what the problem really was.  I'd like to keep after it.

I tried configuring with a trailing "/" on a Red Hat 8.0 box here, and
it seemed to work just fine.  You did not specify what Red Hat release
you were using, but I suspect that idea is a dead end.

You could investigate further without having to reinitdb, just try the
CREATE FUNCTION command in psql:

CREATE OR REPLACE FUNCTION dummy (INTEGER, INTEGER, CSTRING, CSTRING,INTEGER)
RETURNS VOID AS '$libdir/ascii_and_mic', 'ascii_to_mic' LANGUAGE 'c' STRICT;

I expect this will fail as before.  Could you strace the attached
backend process while it's trying to do this command?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Thomas Borg SallingDate: 2004-02-02 20:42:17
Subject: Re: BUG #1072: "$libdir/ascii_and_mic": No such file or directory
Previous:From: Thomas Borg SallingDate: 2004-02-02 18:19:59
Subject: Re: BUG #1072: "$libdir/ascii_and_mic": No such file or directory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group