Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Jul 2017 13:32:17 -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:  <20170722173217.x2nob6ul35jszyor@mutt-hbsd>
In-Reply-To: <20170722153308.3ity33nd5brngbky@mutt-hbsd>
References:  <719BE3EE-00E3-4BAB-A19C-6965BAD67CC9@FreeBSD.org> <20170722153308.3ity33nd5brngbky@mutt-hbsd>

next in thread | previous in thread | raw e-mail | index | archive | help

--oczn2saqtajubuc5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 PRs.
> >=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 PRs
> > 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-amd64=
/910/consoleText
>=20
> I'm working right now on figuring out what caused it. I'll report back
> when I know more.

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.

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

--oczn2saqtajubuc5
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAllzjB4ACgkQaoRlj1JF
bu7YYQ//QWDes5Igo3mJFwCRKZCSehjD8WKVMzEyRYERYja8g1RqsvOWLxH4rJVM
9tNq2gDcAN4KsAIRY9IGIGxztSLIKtr0DqJxdi48R+OO+CkfqhMoizoOzbkCp5T7
bprjuKH9GzaXVkxyqTUWuBhylm3BQyyP+GmkYU/p+e+e4PcnkflN7mevKPWUiCPL
a2+iOV8g45dCiuxc1qAfTIQwuVoJulnNGsCRZXINqCMJR4xkUtaS57dYME817ZbK
owP6MttPKfYRb3hW1ZY+o/9wddBq7Ndv9UbPBu8KZdL9DX+2bJrn0T1Y355Dj3Py
2UDMdNV6dHte75L0iszG4uBLSRClfDiq77FlQ66utCZgIn6MgdBPc1uGd8q68bOV
ceVcvLTpkdmPZ8mC6E80heV28/AaiNk84RcNGmQXNBr8Ky9ThCmujuOEYoSfQoNj
byqauQkAYzKfMGCy7ZgpWo0lemu6hEwVA0n0ILePmCeb5kOOCnHY8gnh1C9+a+69
f4oR/JcBQZM2uObFsLcMI4GNARcxzzPKjcLGy7ENuL9zZXvCexzDwL7ZRKRGiXtz
eHWBzuGOLVBcYLMPulYVby9gFcL6V8WeSa8DXvWY6qSkAoi1uili0jQ7nqahBMOa
nnDQC3PwOTiKDHNNkDOMoiwrVGIamRzPHuuE2oHP2C6hOXaLHL8=
=TUGW
-----END PGP SIGNATURE-----

--oczn2saqtajubuc5--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170722173217.x2nob6ul35jszyor>