Date: Tue, 19 Jan 2016 11:46:44 -0800 From: Mark Millard <markmi@dsl-only.net> To: Ian Lepore <ian@freebsd.org> Cc: Tom Vijlbrief <tvijlbrief@gmail.com>, fehrist@codeghar.com, 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: <D058186F-3232-4215-96B9-E1A253F12CBE@dsl-only.net> In-Reply-To: <1453217670.46848.83.camel@freebsd.org> 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> <1453217670.46848.83.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-Jan-19, at 7:34 AM, Ian Lepore <ian at freebsd.org> wrote: >=20 > 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>: >>=20 >>>=20 >>> 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 >>=20 >>=20 >> I am having exactly the same buildworld problem on my RPI which used >> to >> build fine a week ago. >>=20 >> Currently testing the clang380-import branch as suggested to see if >> the >> problem persists. >=20 > 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? >=20 > 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.) >=20 > -- 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? The "rest" were: head/lib/clang.lib.mk head/lib/libc++/Makefile head/usr.bin/clang/clang/Makefile head/usr/bin/clang/lldb/Makefile (head/share/mk/bsd.lib.mk has had use of STATIC_CFLAGS and = STATIC_CXXFLAGS for a long time.) Since 3.8.0 is now also to reported to fail I'll note that my "on rpi2" = rebuild test was based on 3.8.0 and -r294179 for /usr/src and completed = fine (in about 10 minutes under 14.5 hours). But I've consistently used: -target armv6--freebsd11.0-gnueabi -march=3Darmv7a -mcpu=3Dcortex-a7 = -mfloat-abi=3Dsoftfp -mno-unaligned-access in my builds, including that one. So my activities are really a test for = cortex-a7 handling, not armv6. But I had to use 3.8.0 because clang++ 3.7.1 would Bus Error during its = buildworld activities. (I could buildkernel with 3.7.1 just fine.) =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D058186F-3232-4215-96B9-E1A253F12CBE>