| From: | Michael Meskes <meskes(at)topsystem(dot)de> |
|---|---|
| To: | darrenk(at)insightdist(dot)com (Darren King) |
| Cc: | pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker) |
| Subject: | Re: [HACKERS] Shared libs with version numbers. |
| Date: | 1998-04-30 07:25:02 |
| Message-ID: | 199804300725.JAA07406@gauss.topsystem.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Darren King writes:
> Is there any purpose to the version numbers that some ports append
> to a shared lib name, besides keeping different versions around?
Yes. Making sure your application doesn't load an incompatible version of
the lib.
> Using libpq as an example, is there a difference to the system if...
>
> $(MAKE) libpq.so
> $(INSTALL) libpq.so libpq.so.1
> $(LN) libpq.so.1 libpq.so
>
> ...rather than...
>
> $(MAKE) libpq.so.1
> $(INSTALL) libpq.so.1 libpq.so.1
> $(LN) libpq.so.1 libpq.so
No. The file the system knows is libpq.so.1 either way. You might even call
it foo.bar in your Makefile as long as it is installed as libpq.so.1.
Michael
--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 1998-04-30 07:40:57 | s_lock.h patch |
| Previous Message | Michael Meskes | 1998-04-30 07:22:56 | Re: [HACKERS] ANSI error messages |