Skip site navigation (1) Skip section navigation (2)

Shared libs with version numbers.

From: darrenk(at)insightdist(dot)com (Darren King)
To: pgsql-hackers(at)postgresql(dot)org
Subject: Shared libs with version numbers.
Date: 1998-04-29 19:50:21
Message-ID: 9804291950.AA71342@ceodev (view raw or flat)
Thread:
Lists: pgsql-hackers
Silly question since I work with aix and it doesn't appear to use
the version numbers for shared libs...

Is there any purpose to the version numbers that some ports append
to a shared lib name, besides keeping different versions around?

I've managed to move the port specific code from all of the various
interfaces that make shared libs, but I'd like to understand the
rhyme/reason before I post a patch that breaks all other ports.

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

???

If no difference to the system, the former is _much_ easier to add
shared lib support for aix and use the %.$(DLSUFFIX) rules in the
port Makefiles.

This would be perhaps the final step to removing $(PORTNAME) from the
code, these Makefiles would not have to be generated by configure, and
makes the interfaces/* Makefiles much cleaner.

darrenk

Responses

pgsql-hackers by date

Next:From: Phil ThompsonDate: 1998-04-29 21:07:53
Subject: Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes
Previous:From: David GouldDate: 1998-04-29 19:38:05
Subject: Re: [HACKERS] CVSup help??

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group