From: Reiner Herrmann <reiner@reiner-h.de>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: musl 1.1.16 build failure on armhf
Date: Sat, 7 Jan 2017 16:19:27 +0100 [thread overview]
Message-ID: <20170107151927.GN19319@reiner-h.de> (raw)
In-Reply-To: <20170104213646.GS1555@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On Wed, Jan 04, 2017 at 04:36:46PM -0500, Rich Felker wrote:
> On Wed, Jan 04, 2017 at 10:27:49PM +0100, Reiner Herrmann wrote:
> > On Wed, Jan 04, 2017 at 04:06:09PM -0500, Rich Felker wrote:
> > > The error is from gas; do you know the binutils version? Also, what
> > > -march is gcc configured for?
> >
> > Thanks for the binutils hint. I just tried some older versions, and
> > found out that it builds fine with binutils 2.27.51.20161102-1, but
> > no longer with 2.27.51.20161105-1.
>
> Can you find the commit that broke it and figure out if it's a
> binutils bug or an intentional change we need to find a way to work
> with?
Someone posted the bug also on the binutils mailinglist [0], and found
the commit which broke it [1].
I now built binutils 2.27.51.20161105-1 with this commit reverted, and
was able to build musl.
[0] https://sourceware.org/ml/binutils/2017-01/msg00081.html
[1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=bada43421274615d0d5f629a61a60b7daa71bc15
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-01-07 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 20:51 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 [this message]
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
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=20170107151927.GN19319@reiner-h.de \
--to=reiner@reiner-h.de \
--cc=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).