From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] bat isn't linked against libonig
Date: Tue, 26 May 2020 18:20:40 +0200 [thread overview]
Message-ID: <20200526162040.N1ODX3kEW2gJvY_qJC_A6xVKfkoITtGWYZPL5t6I1tI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22322@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Closed issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/22322
Description:
### System
* xuname: Void 5.6.14_1 x86_64 GenuineIntel notuptodate rrFFFFFFFFFFFFFF
* package: bat-0.15.1
### Expected behavior
It should depend on libonig from oniguruma.
### Actual behavior
It doesn't link agains libonig, probably builds its own version, even though `oniguruma-devel` is in `makedepends`.
### Steps to reproduce the behavior
```
$ ldd /usr/bin/bat
linux-vdso.so.1 (0x00007ffea05d4000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f87f793e000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f87f777b000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f87f7776000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f87f7755000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f87f773b000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f87f75f6000)
/lib/ld-linux-x86-64.so.2 (0x00007f87f8014000)
```
The fix can go together with an update. It's 0.15.3 now.
prev parent reply other threads:[~2020-05-26 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 15:55 [ISSUE] bat isn't linked agains libonig ericonr
2020-05-26 15:58 ` bat isn't linked against libonig ericonr
2020-05-26 16:20 ` ericonr
2020-05-26 16:20 ` ericonr [this message]
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=20200526162040.N1ODX3kEW2gJvY_qJC_A6xVKfkoITtGWYZPL5t6I1tI@z \
--to=ericonr@users.noreply.github.com \
--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).