From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
---|---|
To: | "Kevin Brown *EXTERN*" <kevin(at)sysexperts(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] Fix linking of OpenLDAP libraries |
Date: | 2006-09-12 07:03:42 |
Message-ID: | 52EF20B2E3209443BC37736D00C3C1380A4DD643@EXADV1.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kevin Brown wrote:
>>> Let me expand a little on some of the peculiarities of
>>> shared libraries on AIX:
>>
>>> - A normal AIX shared library is called libXX.a
>>> It is an 'ar' archive that contains the shared object(s).
>>
>> Ah, so the problem really boils down to funny naming conventions.
>> If they use ".a" for both shared and static libraries, how does
anyone
>> tell the difference?
>
> It sounds to me like there is no difference. Notice how his example
> ldd output shows dependencies on specific .o entries within the
> various .a files that reside on the system, rather than on the .a
> files as a whole. If those entries had been statically linked then
> they wouldn't have shown up in the ldd output at all.
That is not entirely true.
The difference between a static and a shared library on AIX
is that the *.o files in a dynamic library are dynamic objects,
produced by the linker (what is called *.so in Linux), and the
*.o files in a static library are the output of the compiler
(what is called *.o in Linux).
What IS true is that you can do a static build against a dynamic
library. Against a static library you can only do static builds.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-09-12 08:36:42 | Re: Lock partitions |
Previous Message | Tom Lane | 2006-09-12 04:52:39 | Re: [HACKERS] Resurrecting per-page cleaner for btree |