From: crtxcr <crtxcr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nextcloud-client fails to build
Date: Sun, 11 Dec 2022 18:01:19 +0100 [thread overview]
Message-ID: <20221211170119.jQvxzErhLgF08MyA_AKP3AebpXEPOXi0FNqbJAESWC0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39467@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
New comment by crtxcr on void-packages repository
https://github.com/void-linux/void-packages/issues/39467#issuecomment-1345605097
Comment:
I can reproduce this. I discovered this issue report because building "poppler"
fails with the exact same error message. So at least 2 packages are now affected
by this.
```
usr/bin/ld: /usr/lib/libz.a(deflate.o): warning: relocation against `z_errmsg' in read-only section `.text'
/usr/bin/ld: /usr/lib/libz.a(zutil.o): relocation R_X86_64_PC32 against symbol `z_errmsg' can not be used when making a shared object; recompile with -fPIC
```
Seems in both cases the build system (cmake) finds libz.a instead of libz.so, for whatever reason.
next prev parent reply other threads:[~2022-12-11 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 15:36 [ISSUE] " Gottox
2022-10-04 2:06 ` sgn
2022-12-11 17:01 ` crtxcr [this message]
2022-12-11 17:19 ` paper42
2022-12-12 7:50 ` crtxcr
2024-02-13 23:39 ` KaiJan57
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=20221211170119.jQvxzErhLgF08MyA_AKP3AebpXEPOXi0FNqbJAESWC0@z \
--to=crtxcr@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).