From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] use .object_arch to declare the architecture of the object file
Date: Sun, 5 Feb 2017 18:40:47 -0500 [thread overview]
Message-ID: <20170205234047.GW1533@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170204141947.5208-1-reiner@reiner-h.de>
On Sat, Feb 04, 2017 at 03:19:47PM +0100, Reiner Herrmann wrote:
> musl fails to build for arm with current binutils (since commit bada434).
> Szabolcs Nagy suggested to use .object_arch for declaring the architecture
> of the object file, instead of .arch.
>
> See also: https://sourceware.org/ml/binutils/2006-09/msg00054.html
> ---
> src/thread/arm/atomics.s | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/thread/arm/atomics.s b/src/thread/arm/atomics.s
> index 202faa4a..101ad391 100644
> --- a/src/thread/arm/atomics.s
> +++ b/src/thread/arm/atomics.s
> @@ -84,7 +84,7 @@ __a_gettp_cp15:
> bx lr
>
> /* Tag this file with minimum ISA level so as not to affect linking. */
> -.arch armv4t
> +.object_arch armv4t
> .eabi_attribute 6,2
What's the earliest version of binutils that supports this? If it's a
newish feature we can't just unconditionally switch... (ARM is
infamous for that kind of breakage...) But if it's been around for a
really long time (long enough that older binutils versions are
seriously broken) it doesn't matter.
Rich
next prev parent reply other threads:[~2017-02-05 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 20:51 musl 1.1.16 build failure on armhf Reiner Herrmann
2017-01-04 21:06 ` Rich Felker
2017-01-04 21:13 ` Reiner Herrmann
2017-01-04 21:27 ` Reiner Herrmann
2017-01-04 21:36 ` Rich Felker
2017-01-07 15:19 ` Reiner Herrmann
2017-01-09 13:02 ` Szabolcs Nagy
2017-02-04 14:19 ` [PATCH] use .object_arch to declare the architecture of the object file Reiner Herrmann
2017-02-05 23:40 ` Rich Felker [this message]
2017-02-06 10:21 ` Szabolcs Nagy
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=20170205234047.GW1533@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).