makes you wonder what possible use a MH_DYLIB library might serve
Martin
______________________________________________
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Fri, 15 May 2009 08:36:48 +0800
> From: craig@postnewspapers.com.au
> To: tgl@sss.pgh.pa.us
> CC: lists@groll.co.za; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Failure during initdb - creating dictionaries ... FATAL: could not access file "$libdir/libdict_snowball": No such file or directory
>
> Tom Lane wrote:
>
> > 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.
>
> If I recall correctly from porting a plugin-based app to Mac OS X a few
> years ago, there are issues with dlopen(...) on .dylib libraries.
>
> I seem to remember having issues getting dylibs to resolve symbols from
> the loading executable and already-loaded libraries; they wanted to
> resolve all symbols as direct dependencies. I needed to use a .so to get
> the library to resolve symbols in the loading application.
>
> A quick bit of reading shows that:
>
> - The extension doesn't matter, the OS doesn't care
>
> - The library type, MH_DYLIB or MH_BUNDLE, is controlled by how
> it's built only
>
> - MH_DYLIB won't resolve symbols from the loading executable
> and can't be unloaded, whereas MH_BUNDLE does and can.
>
> - Most libraries on Mac OS X are MH_DYLIB
>
> Found some info at:
>
> http://developer.apple.com/documentation/DeveloperTools/Conceptual/MachORuntime/Reference/reference.html#//apple_ref/doc/uid/20001298-BAJHHFFF
>
> under Fields, section "filetype"
>
> --
> Craig Ringer
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
Hotmail® has a new way to see what's up with your friends.
Check it out.