From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] build-style: go: allow pie
Date: Mon, 23 Nov 2020 19:18:45 +0100 [thread overview]
Message-ID: <20201123181845.5LoVyVpgUDSEWUXK0mKR_GhUDSGeSDSoi6KpqFd8nWg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24841@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/24841#issuecomment-732338818
Comment:
I think the issue above breaks this proposal completely, unless we can reliably hunt them down.
On the other hand, templates like rclone could be built with PIE and that would solve the issue they had ( https://github.com/ericonr/void-packages/tree/rclone ). So I think we should push forward with a simple way for go binaries to be built with PIE, but not change any defaults yet.
@void-linux/pkg-committers thoughts?
next prev parent reply other threads:[~2020-11-23 18:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 0:35 [PR PATCH] " sgn
2020-09-12 0:37 ` sgn
2020-09-12 0:42 ` sgn
2020-09-12 0:42 ` sgn
2020-09-12 0:45 ` [PR PATCH] [Updated] " sgn
2020-09-12 0:45 ` sgn
2020-09-12 1:01 ` sgn
2020-09-12 1:07 ` sgn
2020-09-12 4:26 ` shizonic
2020-09-19 3:42 ` [PR PATCH] [Closed]: " sgn
2020-11-14 6:23 ` ericonr
2020-11-14 6:29 ` sgn
2020-11-14 6:32 ` ericonr
2020-11-14 18:01 ` ericonr
2020-11-14 18:03 ` ericonr
2020-11-23 18:18 ` ericonr
2020-11-23 18:18 ` ericonr [this message]
2020-11-23 18:19 ` ericonr
2020-11-23 20:19 ` ericonr
2020-11-24 0:15 ` sgn
2020-11-24 0:20 ` ericonr
2020-11-24 0:20 ` ericonr
2020-12-07 0:03 ` [PR PATCH] [Closed]: " sgn
2021-03-16 13:20 ` travankor
2021-04-09 0:17 ` [PR PATCH] [Closed]: " sgn
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=20201123181845.5LoVyVpgUDSEWUXK0mKR_GhUDSGeSDSoi6KpqFd8nWg@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).