> "John David Anglin" <[EMAIL PROTECTED]> writes: > > > > On hpux, libcrypt is only available as an archive library. Thus, it's > > not particularly a great idea to linked it into a shared library. > > Do you mean it can't be used at all from a shared library? Might have > to exclude support for it in that case.
In general, linking an archive library into a shared library can lead to problems with duplication of routines and static data. This is a problem if you have two libraries, or a library and main code which both needed to be linked against an archive library. It can be done if the visibility of symbols is limited to library. Looking at libcrypt.a for hpux 10.20, 11.00 and 11.11, it seems to be essentially empty, so it probably doesn't matter or need to be used. -bash-2.05b$ nm /usr/lib/libcrypt.a Symbols from /usr/lib/libcrypt.a[hpux_rel.o]: Name Value Scope Type Subspace DS$hpux_rel |1073741824|static|data |$DATA$ __emptylib | 0|extern|entry |$CODE$ Hope that helps. Dave -- J. David Anglin [EMAIL PROTECTED] National Research Council of Canada (613) 990-0752 (FAX: 952-6602) _______________________________________________ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
