From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] musl toolchains should reject TEXTRELs
Date: Mon, 23 Nov 2020 15:34:20 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26641@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/26641
Description:
### Expected behavior
Given that musl's runtime linker doesn't support TEXTRELs, the linkers used to build packages for musl targets (both cross and native) should be configured to error out at build time when they find TEXTRELs.
### Actual behavior
Issues like #26638 happen. The linker should have caught it.
### Steps to reproduce the behavior
Cross build `rclone` without #26640 and run `readelf -d /path/to/rclone` to see the TEXTREL.
next reply other threads:[~2020-11-23 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 14:34 ericonr [this message]
2021-08-17 16:40 ` Hello71
2021-08-17 17:02 ` Hello71
2022-04-30 2:14 ` github-actions
2022-05-14 2:16 ` [ISSUE] [CLOSED] " github-actions
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-26641@inbox.vuxu.org \
--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).