Date: Sat, 22 Jul 2017 13:38:13 -0400 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: HEADS-UP: Merged llvm/clang 5.0.0 into -CURRENT (as of r321369) Message-ID: <20170722173813.4jixxgn5mtwajff5@mutt-hbsd> In-Reply-To: <20170722173217.x2nob6ul35jszyor@mutt-hbsd> References: <719BE3EE-00E3-4BAB-A19C-6965BAD67CC9@FreeBSD.org> <20170722153308.3ity33nd5brngbky@mutt-hbsd> <20170722173217.x2nob6ul35jszyor@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
--r2v2yxdv6waosvc4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 22, 2017 at 01:32:17PM -0400, Shawn Webb wrote: > On Sat, Jul 22, 2017 at 11:33:08AM -0400, Shawn Webb wrote: > > On Sat, Jul 22, 2017 at 02:36:03PM +0200, Dimitry Andric wrote: > > > Hi, > > >=20 > > > I have merged clang, llvm, lld, lldb, compiler-rt and libc++ 5.0.0 > > > (trunk r308421) into head. Universe builds went just fine, but if you > > > encounter any snags during world and/or kernel builds, please file PR= s. > > >=20 > > > Since upstream has just created their 5.0.0 release branch, this is a > > > good month to shake out any remaining issues for FreeBSD. If you are > > > certain bugs or regressions you encounter are due to upstream, file P= Rs > > > there, but otherwise, just report them on the FreeBSD bug tracker. > >=20 > > Hey Dimitry, > >=20 > > Thank you very much for your hard work and dedication to bringing the > > llvm toolchain to FreeBSD. > >=20 > > I haven't nailed down whether it's SafeStack, CFI, or using lld as the > > default linker, but it looks like we in HardenedBSD are getting an > > undefined symbol during buildworld. > >=20 > > Here's the logfile: > >=20 > > http://jenkins.hardenedbsd.org:8180/jenkins/job/HardenedBSD-CURRENT-amd= 64/910/consoleText > >=20 > > I'm working right now on figuring out what caused it. I'll report back > > when I know more. >=20 > Found the culprit: WITH_LLD_BOOTSTRAP. It looks like when > MK_LLD_BOOTSTRAP is set to yes, then you get the error in the Jenkins > log above. At least, on amd64. I do _not_ get the error on arm64. I forgot to mention that WITH_LLD_IS_LD is set, too. I haven't tested WITH_LLD_BOOTSTRAP && WITHOUT_LLD_IS_LD. Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --r2v2yxdv6waosvc4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAllzjYUACgkQaoRlj1JF bu5q0A/8DpM6dqOfjXvYYjjFeXrt6FCAXkHr97y8hwzqGMZ1wbn9Gpie+LgaI7y7 xHi6c4I1fkQ4dyF5F0KlR1IF2kwss5vFe/fu/IqBurZFTGIvcye3wQMW9Xbv4Fdb C7kJubC83/ZeJdhgtdJ4dttZoks492HK2MrCBgBzjacQcS3yg32u2uv6kuV272ek d4+YJb/smha6ZsWUUPFdcqyFHCqFkTZJJk/Np6wokI6+kzV1KN0NqCrXLhqU0bRr bIM/cMj60xCtmd8QNPtJM7cn9x8chMN7uKiSsvW2LBIEaFSGmPljveSMMJBZrrba B0GPVwhUIq9J69ofa8qWcJl5qvpEZVtEWst0BnoiZqlcYLFgy4757oxw27hX1DfO ak1Dyktix8PHxNPLoJanmsEg+mqE4mXe29jk+bYnHIk0cjRivqeFKmPcqOOX5Q8c k/sa4BphXklv77OPxurZtjW+45WN37ETkAwRoKOzqr6+gH9IhSV0X2ahlvmVkYyw 9PapLiYePkYLdvNaT306AdA5A+pha7v0kttzm/AgH0KdCQXu+4KwFaMulMKUKope mBsnjRso/p8oUQ2PVPEJONYXzVaMU1hrqhPOpNEBApI0jSAGvUetIFBhtAITaS8r oQtryetwiXxakwUBX5NPtALn9ElRzTurTLUxC2u0kAQkBIXZ1Fc= =X0Ja -----END PGP SIGNATURE----- --r2v2yxdv6waosvc4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170722173813.4jixxgn5mtwajff5>