Date: Wed, 8 Apr 2020 23:21:02 +0000 From: "Sergey A. Osokin" <osa@freebsd.org> To: Yuri <yuri@rawbw.com> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r531147 - in head/net: . usockets usockets/files Message-ID: <20200408232102.GF76848@FreeBSD.org> In-Reply-To: <ff7294e4-4f69-e53c-b5cf-0152e7c36dab@rawbw.com> References: <202004082101.038L1dCF094577@repo.freebsd.org> <20200408213218.GE76848@FreeBSD.org> <ff7294e4-4f69-e53c-b5cf-0152e7c36dab@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 08, 2020 at 02:48:47PM -0700, Yuri wrote:
> On 2020-04-08 14:32, Sergey A. Osokin wrote:
>
> > I bet we need to have a symbolic link ${PREFIX}/lib/libusockets.so.0 to catch
> > this library with ldconfig(8), right?
>
> No, having the file lib/libusockets.so in combination with USE_LDCONFIG=yes
> should make libusockets.so discoverable by ldconfig(8).
>
> The unrelated problem with such library is that it lacks a SONAME because
> the upstream didn't define it (they only build a static library). I'll ask
> them to make a change on GitHub.
Agree, it's better to have both static and shared objects for a library.
Thanks for the update!
--
Sergey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200408232102.GF76848>