From owner-freebsd-arm@freebsd.org Tue Jan 19 16:14:40 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 33F69A88CD5 for ; Tue, 19 Jan 2016 16:14:40 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B729F1A5E; Tue, 19 Jan 2016 16:14:39 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id 123so98105290wmz.0; Tue, 19 Jan 2016 08:14:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=kN6UxEYc6bLeJhOo/YD0ag2Cwrf++5JuQ0jy4cqEQ6A=; b=Xo2v9AunPu0DHRTOKqd/mj8kbeyyVWMMefynG/7Kb3cP7twRlu3cy/DdhIHHXltE6l lJnCgu2waahFbxiOMqNYXKAm74ssXtjhE4uKTjvzcocUHdH2/5V0iSxWHu0NWbCmOarY gnXJ62CHCSz0u6KM+POlU04mZyzWwS9hzlCBnFi3u6nMYqO+NOrIbROcZnjBjgHPDpRj Xs8BFO7FjDYBuBXruV8C3yj/0EKciP4R8SoEYsl1s9e4jn4ZcjNa7Mejz/HY7DGkcp3v //nvZAshbeJpf/RC5Pxr3DO3a1lvn86HWtl6chP77Y8V+5NExxe7mhFTc3+yoQATnZxq ZLbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=kN6UxEYc6bLeJhOo/YD0ag2Cwrf++5JuQ0jy4cqEQ6A=; b=W90I0L/tMMv92kXVKutXCZz2CjHn5zeGcUKimkUjMbL9FBSfNsEPQ0byar60P51VQO hITZsW7GOOUCdb831QUUA+1oKraewB73Iq8Tlwvr1sn82c5pfQDNMXJ2bHKu7dd7CDY4 rjAdr48HX10IUEP3Rl2UmqQSQAJOXoUhceJjUqVnKHtphfDJFN8aY3twkX1pvbGsJGzl EKnGnz2Ult70wt7RkAKTjOUnv7DexXlL5tMcQU0UCTTHmIZr0lUDt4UV5yws4/p5fZjZ TEeJE2rVzCK0bNfRqYvoHQ4PmTH44/O4oigi+k/YO1UVRrs6EJ0Ax4cYwHa2MH5uZ5mY ME7w== X-Gm-Message-State: ALoCoQn43xtY7cG64gmPeITCZ8kUpYEU+DMJhnK97Q7wHrSuozT5v7SgqsI43RvL2eMW4sN9lUjy/HRhb9FRKSq5+PN8MeJz0A== X-Received: by 10.194.175.104 with SMTP id bz8mr29277400wjc.8.1453220078273; Tue, 19 Jan 2016 08:14:38 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: <1453217670.46848.83.camel@freebsd.org> From: Tom Vijlbrief Date: Tue, 19 Jan 2016 16:14:28 +0000 Message-ID: Subject: Re: make buildworld failed with error "relocation truncated to fit: R_ARM_JUMP24 against symbol `_fini'" To: Ian Lepore , Mark Millard , fehrist@codeghar.com Cc: freebsd-arm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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 16:14:40 -0000 clang 3.8 makes no difference, same error. I had to restart the makeworld due to another issue and did this with NO_CLEAN=YES to speed things up The log is here: http://www.v7f.eu/public/freebsd/world.log Note that /usr/src symlinks to /media/swan/src which symlinks to /media/swan/github/freebsd, so that is a bit confusing I will restart it again without the NO_CLEAN and with the default 3.7.1 and in the /media/swan/github/freebsd directory for a clean complete log... Op di 19 jan. 2016 om 16:34 schreef Ian Lepore : > On Tue, 2016-01-19 at 11:58 +0000, Tom Vijlbrief wrote: > > Op ma 18 jan. 2016 20:37 schreef Mark Millard : > > > > > > > > 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 > >