From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: bearssl: fix libbearssl.so.0 => not found
Date: Mon, 16 Sep 2019 19:57:40 +0200 [thread overview]
Message-ID: <20190916175740.jp9gxZ_AusKzJUGB7NItMSmwE76aW3ggVN_MFKliZds@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14470@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
New comment by concatime on void-packages repository
https://github.com/void-linux/void-packages/pull/14470#issuecomment-531887693
Comment:
Trying to run my own app based on BearSSL.
```sh
xbps-query -f bearssl
# /usr/bin/brssl
# /usr/lib/libbearssl.so.0.6
# /usr/share/licenses/bearssl/LICENSE
xbps-query -f bearssl-devel
# /usr/include/bearssl.h
# /usr/include/bearssl_aead.h
# /usr/include/bearssl_block.h
# /usr/include/bearssl_ec.h
# /usr/include/bearssl_hash.h
# /usr/include/bearssl_hmac.h
# /usr/include/bearssl_kdf.h
# /usr/include/bearssl_pem.h
# /usr/include/bearssl_prf.h
# /usr/include/bearssl_rand.h
# /usr/include/bearssl_rsa.h
# /usr/include/bearssl_ssl.h
# /usr/include/bearssl_x509.h
# /usr/lib/libbearssl.a
# /usr/lib/libbearssl.so -> /usr/lib/libbearssl.so.0.6
```
As you see, no `libbearssl.so.0`.
next prev parent reply other threads:[~2019-09-16 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 15:17 [PR PATCH] " voidlinux-github
2019-09-15 15:33 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-15 15:33 ` voidlinux-github
2019-09-15 15:35 ` voidlinux-github
2019-09-15 15:35 ` voidlinux-github
2019-09-15 15:43 ` voidlinux-github
2019-09-15 15:43 ` voidlinux-github
2019-09-15 22:03 ` voidlinux-github
2019-09-15 22:03 ` voidlinux-github
2019-09-15 22:03 ` voidlinux-github
2019-09-15 22:03 ` voidlinux-github
2019-09-15 22:47 ` voidlinux-github
2019-09-15 22:47 ` voidlinux-github
2019-09-16 14:31 ` voidlinux-github
2019-09-16 17:57 ` voidlinux-github [this message]
2019-09-17 8:23 ` [PR PATCH] [Merged]: " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190916175740.jp9gxZ_AusKzJUGB7NItMSmwE76aW3ggVN_MFKliZds@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).