From: IcedQuinn <IcedQuinn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] zimwriterfs, zim-tools: broken symbols
Date: Mon, 08 Feb 2021 23:21:00 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28600@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
New issue by IcedQuinn on void-packages repository
https://github.com/void-linux/void-packages/issues/28600
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*output of ``xuname`` (part of xtools)*
* package:
*affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
* xuname: Void 5.10.13_1 x86_64 GenuineIntel notuptodate rrFF
* packages: zimwriterfs-1.3.7_1, zim-tools-1.2.1_1
### Expected behavior
Tools should display an error since they have no parameters passed to them, but not a symbol lookup error.
### Actual behavior
```
zimwriterfs: symbol lookup error: zimwriterfs: undefined symbol: _ZN3zim6writer7CreatorC2Eb
zimrecreate: symbol lookup error: zimrecreate: undefined symbol: _ZN3zim6writer7CreatorC2Eb
```
### Steps to reproduce the behavior
Install zimwriterfs and/or zim-tools, then attempt to run them. You will get linker errors instead of the application's own error.
next reply other threads:[~2021-02-08 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 22:21 IcedQuinn [this message]
2021-02-09 8:15 ` [ISSUE] [CLOSED] " Johnnynator
2021-02-09 9:28 ` IcedQuinn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28600@inbox.vuxu.org \
--to=icedquinn@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).