From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [TRACKING-upstream] go: enable PIE builds for Go executables
Date: Tue, 29 Sep 2020 03:50:46 +0200 [thread overview]
Message-ID: <20200929015046._gWuPzT66TxWpokYYDuPJnDVMjJWsdk2uW_gOKZyn60@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20854@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
There's a closed pull request on the void-packages repository
[TRACKING-upstream] go: enable PIE builds for Go executables
https://github.com/void-linux/void-packages/pull/20854
Description:
Fixed up version of #20450
Both Arch Linux and Alpine already implement this feature. Arch has a package called go-pie that's used for most of their PKGBUILDs, while the only version of Go on Alpine is one capable of producing PIE binaries.
On Arch: https://www.archlinux.org/packages/community/x86_64/go-pie/
On Alpine: https://pkgs.alpinelinux.org/package/edge/community/x86_64/go
The patch used here is actually adapted from the one used by Arch, and if adopted can allow us to remove the nostrip flag from the go build_style.
I'm getting some weird build output, where it says
loadinternal: cannot find runtime/cgo
so I'm not completely certain that it's 100% complete. Building a program that uses cgo does work cleanly, so I'm not sure what it means.
prev parent reply other threads:[~2020-09-29 1:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 20:57 [PR PATCH] " ericonr
2020-04-12 11:02 ` travankor
2020-04-12 19:03 ` ericonr
2020-04-12 19:04 ` ericonr
2020-04-12 19:32 ` q66
2020-04-12 20:49 ` travankor
2020-04-12 21:09 ` ericonr
2020-04-18 5:39 ` ericonr
2020-04-19 6:09 ` [PR PATCH] [Updated] " ericonr
2020-04-19 6:16 ` ericonr
2020-04-19 6:22 ` ericonr
2020-04-20 3:37 ` the-maldridge
2020-04-21 4:49 ` ericonr
2020-04-21 4:49 ` [PR PATCH] [Closed]: " ericonr
2020-04-21 4:51 ` ericonr
2020-09-29 1:50 ` [TRACKING-upstream] " ericonr
2020-09-29 1:50 ` ericonr [this message]
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=20200929015046._gWuPzT66TxWpokYYDuPJnDVMjJWsdk2uW_gOKZyn60@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).