From: KaiJan57 <KaiJan57@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] python3 fails to build
Date: Tue, 13 Feb 2024 16:55:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48698@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
New issue by KaiJan57 on void-packages repository
https://github.com/void-linux/void-packages/issues/48698
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.16_1 x86_64-musl GenuineIntel uptodate rFFF
### Package(s) Affected
python3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
xbps-src builds python3
### Actual behaviour
python3 build fails with clean masterdir, hostdir; error message:
```
gcc -shared -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -fno-semantic-interposition -fprofile-generate Modules/zlibmodule.o -L/usr/lib -lz -o Modules/zlib.cpython-312-x86_64-linux-musl.so
/usr/bin/ld: /usr/lib/libz.a(zutil.o): warning: relocation against `z_errmsg' in read-only section `.text'
/usr/bin/ld: /usr/lib/libz.a(deflate.o): relocation R_X86_64_PC32 against symbol `z_errmsg' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
### Steps to reproduce
1. clone void-packages
2. run xbps-src binary-bootstrap
3. run xbps-src pkg python3
4. it fails, even if masterdir and hostdir are cleaned
next reply other threads:[~2024-02-13 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 15:55 KaiJan57 [this message]
2024-02-13 18:21 ` chrysos349
2024-02-13 18:24 ` chrysos349
2024-02-13 19:25 ` [ISSUE] [CLOSED] " KaiJan57
2024-02-13 19:25 ` 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48698@inbox.vuxu.org \
--to=kaijan57@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).