[1595] in Kerberos_V5_Development
Re: util/makeshlib
daemon@ATHENA.MIT.EDU (Ezra Peisach)
Fri Aug 16 08:48:05 1996
To: Tom Yu <tlyu@MIT.EDU>
Cc: krbcore@MIT.EDU
In-Reply-To: Your message of "Thu, 15 Aug 1996 23:44:10 EDT."
<199608160344.XAA19535@dragons-lair.MIT.EDU>
Date: Fri, 16 Aug 1996 08:48:00 EDT
From: Ezra Peisach <epeisach@MIT.EDU>
Hmm... Assuming that the kdb was rewritten to use the db API - what would
that do for creating shared libraries? I would assume that we
would need to specify that certain functions were not available at the
creation of the library (in fact there was some old cruft in the
Makefile.in in some places to do this).
Instead of changing util/makeshlib, wouldn't a better place to make the
change be in the lib/kdb5/Makefile.in in terms of passing the flags to the
makeshlib.... Of course, the other logical question is what other libraries
depend on the libkdb5 - and need to get things right.
I guess a different question would be - is there a better way to mix
shared and non-shared libraries together? Is there a flag that can
be used on all platforms to indicate that notice the symbols from the
static library - but don't copy the elements into your own library?
Oh yeah - BTW - there is already a "LD_UNRESOLVED_PREFIX" defined that can be
used in passing arguments to makeshlib - to indicate that they don't exist...
However, I think there may be problems with this under AIX....
Ezra
