Date: Tue, 19 Jan 2016 08:34:30 -0700 From: Ian Lepore <ian@freebsd.org> To: Tom Vijlbrief <tvijlbrief@gmail.com>, Mark Millard <markmi@dsl-only.net>, fehrist@codeghar.com Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: make buildworld failed with error "relocation truncated to fit: R_ARM_JUMP24 against symbol `_fini'" Message-ID: <1453217670.46848.83.camel@freebsd.org> In-Reply-To: <CAOQrpVeWUHNUoXAF_ko9NwXQcCkfuZNNbpFAJHTGnY_p5uu5sg@mail.gmail.com> References: <3E1CC674-D534-4C33-8C96-CA9E584931C0@dsl-only.net> <569D2557.3060802@codeghar.com> <C9C41590-3798-45D2-8F47-2A5AB4AA137A@dsl-only.net> <374A0F64-E3FC-42F1-AC03-DF8F88269AEB@dsl-only.net> <569D2D63.8030301@codeghar.com> <FF2B458C-5776-4797-9056-4CAA8DFECC43@dsl-only.net> <CAOQrpVeWUHNUoXAF_ko9NwXQcCkfuZNNbpFAJHTGnY_p5uu5sg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1453217670.46848.83.camel>