Date: Mon, 18 Jan 2016 09:30:27 -0800 From: Hamza Sheikh <fehrist@codeghar.com> To: Toby <misc.lists@fsck.ch> Cc: freebsd-arm <freebsd-arm@freebsd.org>, markmi@dsl-only.net Subject: Re: make buildworld failed with error "relocation truncated to fit: R_ARM_JUMP24 against symbol `_fini'" Message-ID: <569D2133.2000103@codeghar.com> In-Reply-To: <569C8B54.8040306@fsck.ch> References: <569C1D2E.6040401@codeghar.com> <478fef0c3db.611911c6@mail.schwarzes.net> <569C8B54.8040306@fsck.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
> buildworld fails in the same way for me, and my /tmp and /var/tmp are > 1GB each, /usr/obj is around 4GB and / has around 700MB of free space > before starting the build. I have changed /tmp to use tmpfs. $ cat /etc/fstab /dev/mmcsd0s1 /boot/msdos msdosfs rw,noatime 0 0 /dev/mmcsd0s2a / ufs rw,noatime 1 1 #md /tmp mfs rw,noatime,-s50m 0 0 md /var/log mfs rw,noatime,-s15m 0 0 md /var/tmp mfs rw,noatime,-s10m 0 0 tmpfs /tmp tmpfs rw,mode=777 0 0 > I did a successful buildworld with the same configuration just before > the latest batch of security advisories came in. Because of all the > advisories, I updated src and did another buildworld. It has failed since. Mark Millard[1] has identified possible issues with /usr/local/raspbsd being present in the error message. As you can see I have no such path. $ ls /usr/local/raspbsd ls: /usr/local/raspbsd: No such file or directory $ ls /usr/local bin etc include lib libdata man openssl sbin share > (error message added again for reference) > /usr/lib/crt1.o: In function `finalizer': > /usr/src/lib/csu/arm/crt1.c:(.text+0x1ec): relocation truncated to fit: > R_ARM_JUMP24 against symbol `_fini' defined in .fini section in > /usr/lib/crti.o > c++: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 > > Stop. > make[4]: stopped in /usr/src/usr.bin/clang/clang > *** Error code 1 It looks like you're using vanilla FreeBSD unlike me; I'm using RaspBSD install/bootable image. Since we're hitting the same issue I'm guessing it might not matter which install image is used. [1] https://lists.freebsd.org/pipermail/freebsd-arm/2016-January/013053.html -- Hamza Sheikh Twitter: @aikchar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?569D2133.2000103>