From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: binutils 2.35.1
Date: Thu, 07 Jan 2021 16:42:50 +0100 [thread overview]
Message-ID: <20210107154250.OlvNmeO5ZSObiMkpT5z6vbxuIdNMrSmRzERso_JKRCc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27727@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
There's a merged pull request on the void-packages repository
binutils 2.35.1
https://github.com/void-linux/void-packages/pull/27727
Description:
we should probably merge this before https://github.com/void-linux/void-packages/pull/24258
I overhauled the template, and enabled (or made explicit) various options that are useful, including RELRO by default (other distros generally use this already). Our ancient PIC rebuild hack is now not needed thanks to `--with-pic`; universal options are now always used universally, and target specific options (e.g. secureplt) are target specific. Additionally, separate build directory is always used.
I tried enabling testsuite but especially on musl this is too much of a pain in the ass and not worth it. There are multiple tests we would have to patch out, even on glibc, and I don't think it's great to carry in a large number of patches just to get all this fragile mess fixed up. This is, however, not a new situation.
Also, the cross-toolchain build style has been updated to unify the binutils configure arguments a little. An omission is `--enable-threads`, which is only used by gold, which is disabled in crosstargets. I think it would be a good idea to disable it in binutils itself as well (it would seem upstream is considering deprecating it), but that's for another time.
Otherwise, I tested this on all ppc targets (32-bit, 64-bit, little endian, big endian, glibc, musl) and it seems to be working fine there (i'm currently building packages with it on my server). I also cross-compiled to `aarch64`, `aarch64-musl`, `armv7l` and `armv6l-musl`. Testing on x86(_64) by other people would be good before we merge this.
prev parent reply other threads:[~2021-01-07 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 0:58 [PR PATCH] " q66
2021-01-07 1:02 ` [PR PATCH] [Updated] " q66
2021-01-07 2:24 ` q66
2021-01-07 15:39 ` [PR PATCH] [Updated] " q66
2021-01-07 15:42 ` q66 [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=20210107154250.OlvNmeO5ZSObiMkpT5z6vbxuIdNMrSmRzERso_JKRCc@z \
--to=q66@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).