From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: go: enable PIE builds for Go executables
Date: Sun, 19 Apr 2020 08:16:21 +0200 [thread overview]
Message-ID: <20200419061621.JpA5uNIVM5HgknSo7xaYVtZSooOoh0trrVksBJRX27k@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: 1078 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/20854#issuecomment-616050062
Comment:
https://github.com/alpinelinux/aports/commits/master/community/go will give some idea of the apparent fight it is to get Go working properly.
That said, simply setting `GOFLAGS` to the appropriate value made it possible to build Go executables with pie, which can be stripped and checked by the build hooks (no more nostrip/nopie, yay). I have built executables for armv6l and x86_64, and preliminary testing shows them working well on x64, while I still have to test arm. It seems getting the compiler itself to be built with PIE will be harder.
Due to not having any idea about how to test arches that use gccgo (@q66 I imagine you have some experience with this, given your void-ppc project), I tried to keep the environment for that build system as close as possible to the original. If you orient me on testing, we can see if some or any of these changes can be moved to it as well.
@travankor if you want to take a look :)
next prev parent reply other threads:[~2020-04-19 6:16 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 [this message]
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 ` [PR PATCH] [Closed]: " ericonr
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=20200419061621.JpA5uNIVM5HgknSo7xaYVtZSooOoh0trrVksBJRX27k@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).