From owner-freebsd-arm@freebsd.org Tue Jan 19 20:21:49 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 061ABA88DDC for ; Tue, 19 Jan 2016 20:21:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC2AC1591 for ; Tue, 19 Jan 2016 20:21:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 19 Jan 2016 20:21:23 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u0JKKdot009766; Tue, 19 Jan 2016 13:20:39 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1453234839.46848.88.camel@freebsd.org> Subject: Re: make buildworld failed with error "relocation truncated to fit: R_ARM_JUMP24 against symbol `_fini'" From: Ian Lepore To: Mark Millard Cc: freebsd-arm Date: Tue, 19 Jan 2016 13:20:39 -0700 In-Reply-To: References: <3E1CC674-D534-4C33-8C96-CA9E584931C0@dsl-only.net> <569D2557.3060802@codeghar.com> <374A0F64-E3FC-42F1-AC03-DF8F88269AEB@dsl-only.net> <569D2D63.8030301@codeghar.com> <1453217670.46848.83.camel@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 20:21:49 -0000 On Tue, 2016-01-19 at 11:46 -0800, Mark Millard wrote: > On 2016-Jan-19, at 7:34 AM, Ian Lepore wrote: > > > > On Tue, 2016-01-19 at 11:58 +0000, Tom Vijlbrief wrote: > > > Op ma 18 jan. 2016 20:37 schreef Mark Millard < > > > markmi@dsl-only.net>: > > > > > > > > > > > If you can tolerate tracking the 3.8.0 project ( > > > > base/projects/clang380-import ) until 3.8.0 is moved into 11.0 > > > > -CURRENT you > > > > could find out that way if clang 3.8.0 behaves the same in your > > > > context. So > > > > far I've not come up with anything else > > > > > > > > > I am having exactly the same buildworld problem on my RPI which > > > used > > > to > > > build fine a week ago. > > > > > > Currently testing the clang380-import branch as suggested to see > > > if > > > the > > > problem persists. > > > > The most confusing thing about this whole thread (besides the lack > > of > > logs so we're just guessing what's going on) is why this problem is > > suddenly happening on clang 3.7.x (I guess it's 3.7.x here) when > > that > > has never been a problem before? We needed to add the long-call > > option > > when testing clang 3.8, but why do we suddenly need it on clang 3.7 > > that hasn't needed it for months? > > > > This very much has the feel of slapping a bandaid on something that > > needs a better diagnosis (there may be internal bleeding). If we > > don't > > understand why it's failing, it doesn't make sense to try to fix it > > with the "cure" for a different problem. (Maybe we never > > understood > > the clang 3.8 problem.) > > > > -- Ian > > The -mlong-calls were added to 11.0-CURRENT recently. > > -r293648: 2016-Jan-10 (head/lib/csu/arm/Makefile) > -r294031: 2016-Jan-14 (the rest added here) > > May be a problem/incompleteness in the handling -mlong-calls itself? > Are the above the right time frame for the problem starting for > 3.7.1? We've been using clang 3.7 since October. We never needed -mlong-calls until recently. I had thought it was clang 3.8 that triggered the need for -mlong-calls, but now we apparently have a report of clang 3.7.x needing it. So... why? What changed, and why are we blindly reacting without understanding? -- Ian