Re: AW: [HACKERS] shared lib names

From: "Mark Hollomon" <mhh(at)nortelnetworks(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at>, "'hackers(at)postgresql(dot)org'" <hackers(at)postgreSQL(dot)org>
Subject: Re: AW: [HACKERS] shared lib names
Date: 1999-07-16 17:48:48
Message-ID: 378F7080.72A86E3A@americasm01.nt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> writes:
> > Ok, sorry I see the difference now. Those that are for linking are named
> > lib*.so
> > and those that are for dyn loading into postgres don't have the lib.
>
> What? They should all have the "lib" AFAIK --- dynamic loading takes
> the same kind of shared lib as a regular link does on every platform
> I've heard about.

I don't know about 'should' but they definitely are not required
to have it.

As Andreas said, the reason for the 'lib' prefix is to allow the -l
flag to the linker to work. What you pass to dlopen is the path to the
file, so
it can have any name you want. Generally (may be some platform this
isn't true)
you don't even have to have a magic suffix.

--

Mark Hollomon
mhh(at)nortelnetworks(dot)com
ESN 451-9008 (302)454-9008

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas 1999-07-16 17:54:16 Re: new: Makefile.shlib bug and AIX patch
Previous Message Bruce Momjian 1999-07-16 17:25:14 Re: [HACKERS] final #include cleanup