Thread

1. Re: AW: [HACKERS] shared lib names

   Tom Lane <tgl@sss.pgh.pa.us> — 1999-07-16T17:14:19Z

   Zeugswetter Andreas IZ5 <Andreas.Zeugswetter@telecom.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 think you were just fooled by having misspelled the "shlib" variable
   the first time around... or, perhaps, our dynlink support for aix
   is confused too?
   
   			regards, tom lane
   
   

2. Re: AW: [HACKERS] shared lib names

   Mark Hollomon <mhh@nortelnetworks.com> — 1999-07-16T17:48:48Z

   Tom Lane wrote:
   > 
   > Zeugswetter Andreas IZ5 <Andreas.Zeugswetter@telecom.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@nortelnetworks.com
   ESN 451-9008 (302)454-9008