Date: Fri, 29 Dec 2017 15:21:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214864] [exp-run] test build with lld as /usr/bin/ld Message-ID: <bug-214864-13-P3152eknU3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214864-13@https.bugs.freebsd.org/bugzilla/> References: <bug-214864-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214864 --- Comment #68 from commit-hook@freebsd.org --- A commit references this bug: Author: emaste Date: Fri Dec 29 15:20:54 UTC 2017 New revision: 457508 URL: https://svnweb.freebsd.org/changeset/ports/457508 Log: sysutils/e2fsprogs: set LLD_UNSAFE to avoid linking with lld One test fails when this port is linked with lld: d_loaddump: debugfs load/dump test: failed --- d_loaddump/expect 2017-10-16 05:45:45.000000000 +0000 +++ d_loaddump.log 2017-12-28 13:00:42.099973000 +0000 @@ -10,7 +10,7 @@ Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information -test_filesys: 12/64 files (0.0% non-contiguous), 158/512 blocks +test_filesys: 12/64 files (0.0% non-contiguous), 156/512 blocks Exit status is 0 debugfs -R ''dump test_data d_loaddump.ver.tmp'' test.img Exit status is 0 This looks like a very unusual failure and careful investigation into lld's behaviour is warranted, but for now set LLD_UNSAFE to fall back to ld.bfd so the port continues to build for users using lld as /usr/bin/ld. PR: 214864 Approved by: portmgr (LLD_UNSAFE blanket) Sponsored by: The FreeBSD Foundation Changes: head/sysutils/e2fsprogs/Makefile --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214864-13-P3152eknU3>