Date: Wed, 24 Sep 2003 15:40:35 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Daniel Eischen <eischen@vigrid.com> Cc: Freebsd Current <current@freebsd.org> Subject: Re: Fixing -pthreads (Re: ports and -current) Message-ID: <200309241940.h8OJeZC0067604@khavrinen.lcs.mit.edu> In-Reply-To: <Pine.GSO.4.10.10309241517300.23494-100000@pcnet5.pcnet.com> References: <20030924144141.N35442@sasami.jurai.net> <Pine.GSO.4.10.10309241517300.23494-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Wed, 24 Sep 2003 15:19:43 -0400 (EDT), Daniel Eischen <eischen@vigrid.com> said: > Eek, no. Libpthread is libpthread, libthr is libthr, etc. A > symlink doesn't help you anyways because the library/application > becomes dependent on the thing it is symlink'd to, not the > symlink. That depends on what the SONAME entry says.... It is technically feasible to have libpthread.so by a symlink, provided that all three thread libraries cooperate by announcing an SONAME of libpthread.so.N. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309241940.h8OJeZC0067604>