From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 19 Aug 2015 05:59:23 -0700 (PDT) From: oliver To: voidlinux Message-Id: <16733fae-3e2b-4725-92be-6907a363737c@googlegroups.com> In-Reply-To: References: Subject: Re: shlibs error when installing built pkg MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_220_1021356825.1439989163948" ------=_Part_220_1021356825.1439989163948 Content-Type: multipart/alternative; boundary="----=_Part_221_813090561.1439989163948" ------=_Part_221_813090561.1439989163948 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Wednesday, August 19, 2015 at 2:11:17 AM UTC-4, Juan RP wrote: > > > That means that any of its binaries need two shared libraries that aren't > available in the xbps repositories. > > In this case this package specifically needs openssl and the sonames must > be `lib{crypto,ssl}.so.1.0.0`. > > Adding them to `common/shlibs` is a workaround for xbps-src but not enough > with xbps. You'll have to > supply those shared libraries somehow in another pkg (openssl) or in the > same package. > I see - thanks. Makes sense now. Any problem in just symlinking? ------=_Part_221_813090561.1439989163948 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Wednesday, August 19, 2015 at 2:11:17 AM UTC-4, Juan RP= wrote:

Th= at means that any of its binaries need two shared libraries that aren't= available in the xbps repositories.

In this case this package speci= fically needs openssl and the sonames must be `lib{crypto,ssl}.so.1.0.0`.
Adding them to `common/shlibs` is a workaround for xbps-src but not e= nough with xbps. You'll have to
supply those shared libraries someho= w in another pkg (openssl) or in the same package.

I see - thanks. =C2=A0Makes sense now. =C2=A0Any problem = in just symlinking?=C2=A0
------=_Part_221_813090561.1439989163948-- ------=_Part_220_1021356825.1439989163948--