From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10914 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl 1.1.16 build failure on armhf Date: Mon, 9 Jan 2017 14:02:53 +0100 Message-ID: <20170109130253.GK17692@port70.net> References: <20170104205123.GH19319@reiner-h.de> <20170104210609.GQ1555@brightrain.aerifal.cx> <20170104212749.GJ19319@reiner-h.de> <20170104213646.GS1555@brightrain.aerifal.cx> <20170107151927.GN19319@reiner-h.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1483966991 8340 195.159.176.226 (9 Jan 2017 13:03:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 9 Jan 2017 13:03:11 +0000 (UTC) User-Agent: Mutt/1.6.0 (2016-04-01) Cc: Rich Felker To: musl@lists.openwall.com Original-X-From: musl-return-10927-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 09 14:03:03 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cQZbK-0001Bw-Oy for gllmg-musl@m.gmane.org; Mon, 09 Jan 2017 14:03:02 +0100 Original-Received: (qmail 20151 invoked by uid 550); 9 Jan 2017 13:03:05 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 20133 invoked from network); 9 Jan 2017 13:03:04 -0000 Mail-Followup-To: musl@lists.openwall.com, Rich Felker Content-Disposition: inline In-Reply-To: <20170107151927.GN19319@reiner-h.de> Xref: news.gmane.org gmane.linux.lib.musl.general:10914 Archived-At: * Reiner Herrmann [2017-01-07 16:19:27 +0100]: > On Wed, Jan 04, 2017 at 04:36:46PM -0500, Rich Felker wrote: > > 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 the regression was not intentional i think, but that change fixes a real issue. .arch foo x .arch bar y assembles x according to arch foo, and y according to arch bar and the final arch attribute of the object is bar. however there is a second fixup pass in arm gas and that fixes both x and y according to the final object attribute and that can fail on x (the patch happens to tighten some checks there) this may be fixed in gas by considering .arch settings during the second pass, but it is probably non-trivial code change (second pass does not have the context of the original code now) on the musl side a possible workaround is to use the .object_arch directive which only affects the final arch attribute, but not the second pass. (but it has to be evaluated on all the different toolchains and assemblers to do the right thing..)