Re: Failure during initdb - creating dictionaries ... FATAL: could not access file "$libdir/libdict_snowball": No such file or directory - Mailing list pgsql-general

From Tom Lane
Subject Re: Failure during initdb - creating dictionaries ... FATAL: could not access file "$libdir/libdict_snowball": No such file or directory
Date
Msg-id 12592.1242315035@sss.pgh.pa.us
Whole thread Raw
In response to Re: Failure during initdb - creating dictionaries ... FATAL: could not access file "$libdir/libdict_snowball": No such file or directory  (Jonathan Groll <lists@groll.co.za>)
Responses Re: Failure during initdb - creating dictionaries ... FATAL: could not access file "$libdir/libdict_snowball": No such file or directory  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
Jonathan Groll <lists@groll.co.za> writes:
> On Wed, May 13, 2009 at 09:54:56AM -0400, Tom Lane wrote:
>> I find this pretty suspicious.  On my OSX machine, the contents of the
>> pkglibdir directory are all named something.so:
>> dict_snowball.so*                       utf8_and_euc_jp.so*

> And mine are also .so after doing a regular make build with the same
> tarball (with the exception of those whose name starts with lib*). I
> was under the impression that OS X used .dylib for shared libraries(1)
> - look in /usr/lib for example.

I don't recall the details at the moment, but I think we intentionally
didn't adopt the .dylib extension for these files because of some subtle
difference between them and plain shared libraries.  I notice that
"file" describes them as "bundles" whereas what's in /usr/lib seems to
get described as "dynamically linked shared library" ... but the
implications escape my memory.

            regards, tom lane

pgsql-general by date:

Previous
From: Allan Kamau
Date:
Subject: Re: how to extract data from bytea so it is be used in blob for mysql database
Next
From: Steven Lembark
Date:
Subject: Question on inserting non-ascii strings