Date: Tue, 19 Jan 2016 12:37:57 -0800 From: Warner Losh <imp@bsdimp.com> To: Ian Lepore <ian@freebsd.org> Cc: Mark Millard <markmi@dsl-only.net>, 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: <22464834-766A-43F1-A54A-1AFE79DD166C@bsdimp.com> In-Reply-To: <1453234839.46848.88.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> <D058186F-3232-4215-96B9-E1A253F12CBE@dsl-only.net> <1453234839.46848.88.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_041359FB-A7B6-4B37-BDB1-871EEFD8DEAF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 19, 2016, at 12:20 PM, Ian Lepore <ian@freebsd.org> wrote: >=20 > On Tue, 2016-01-19 at 11:46 -0800, Mark Millard wrote: >> 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 >>=20 >> The -mlong-calls were added to 11.0-CURRENT recently. >>=20 >> -r293648: 2016-Jan-10 (head/lib/csu/arm/Makefile) >> -r294031: 2016-Jan-14 (the rest added here) >>=20 >> 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? >=20 > 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. >=20 > So... why? What changed, and why are we blindly reacting without > understanding? They were added to -current because they will be needed with clang 3.8. I don=E2=80=99t think that was sufficiently tested with 3.7.1, which is = why we=E2=80=99re seeing problems. It=E2=80=99s the simplest explanation :) Warner --Apple-Mail=_041359FB-A7B6-4B37-BDB1-871EEFD8DEAF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWnp6lAAoJEGwc0Sh9sBEAXzMP/RnGgyzoRUZDBRuPRnYap1vo MHEkobS0sYyqpFnd7FUy0m1lSgJnRd1Ciytq6WmlpAv3ki65Uog45vrh9cguknqw jUI6548RxbNwouq6npbyjSqWtIUasqTdfqJc9qfFYaYdyMt/zuRDJiHyzScCsqg4 IhTzsnwsY6ARPsgJYTbC+uTY6vOZJibrUOpSPPAFegTKp871jwiRHcy/eqL5uRAW 77q2qyS6gK38uTVSHDMxKRHxXCsAKt74WbZYtI73Otv4cGFbQqyJnhMZ0YEgHCW2 avIUffgxX5I9Hty2CuG9zGJgd6qyLUdHrs/lqsdDuiGFNVK4yViv41n5phv58tSI WZ0OOM3UtVy07iRKZ9D79JwyoWEKZiLhR/9Kby4opWYFdr2d+T0e4LjFFJZY+AGJ au1rFF/dhBt0z0PZ6m8uf+fljsITusQ0j3HPMJmlp2Eh1zw38DD1Yo3BVO93RpeG QE2AcAdFv+LFPn2VICltEGoMsiwnpiT+BoXxC1FOtSifLCjfneLmMYl7oybEG6fn YU0woVJFL0dWF9GapTPD4XhU3NX2buU3ImV0iI5+2Z4HYZkZSuzm4eHWsZjPrRD9 yQIfTNA4Tdrbt9WWmYz+6SS29Q4QYvevRW0ff4AJ7r1babliwEUGgk9/qqviUG4u LkGM1Lrcu1UVgr8SAoNo =UT7x -----END PGP SIGNATURE----- --Apple-Mail=_041359FB-A7B6-4B37-BDB1-871EEFD8DEAF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22464834-766A-43F1-A54A-1AFE79DD166C>