make buildworld failed with error "relocation truncated to fit: R_ARM_JUMP24 against symbol `_fini'"

[Tom Vijlbrief]

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 <ian at freebsd.org>:

> On Tue, 2016-01-19 at 11:58 +0000, Tom Vijlbrief wrote:
> > Op ma 18 jan. 2016 20:37 schreef Mark Millard <markmi at 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
>
>