Date: Sat, 07 Feb 2004 00:07:18 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: das@freebsd.org Cc: current@freebsd.org Subject: Re: HEADS UP: libkse -> libpthread switch Message-ID: <20040207.000718.29363133.imp@bsdimp.com> In-Reply-To: <20040207005520.GA7132@VARK.homeunix.com> References: <20040205072422.GB11291@VARK.homeunix.com> <4023C100.2090305@freebsd.org> <20040207005520.GA7132@VARK.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040207005520.GA7132@VARK.homeunix.com>
David Schultz <das@freebsd.org> writes:
: Maybe I don't understand dynamic linking in FreeBSD well enough,
: but an application that is both statically and dynamically linked
: against the same library seems bizarre and unusual to me.
: Wouldn't the two halves reference different copies of the library,
: breaking things like malloc() and gethostbyname() (in the
: hypothetical case of libc)? I don't see how such a thing could
: possibly work in the first place.
Such a thing is possible if at the time you built library X, it
required library Y shared. You then build program A that requires
library X and Y, but link Y static. Bad things happen after that.
Esp if Y is libc or libc_r.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040207.000718.29363133.imp>