Date: Sat, 22 Jul 2017 22:32:53 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Shawn Webb <shawn.webb@hardenedbsd.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: <79E2E246-88BA-4B0E-BCDA-570D4FA983E2@FreeBSD.org> In-Reply-To: <20170722173813.4jixxgn5mtwajff5@mutt-hbsd> References: <719BE3EE-00E3-4BAB-A19C-6965BAD67CC9@FreeBSD.org> <20170722153308.3ity33nd5brngbky@mutt-hbsd> <20170722173217.x2nob6ul35jszyor@mutt-hbsd> <20170722173813.4jixxgn5mtwajff5@mutt-hbsd>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 22 Jul 2017, at 19:38, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > 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, >>>> >>>> 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. >>>> >>>> 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. >>> >>> Hey Dimitry, >>> >>> Thank you very much for your hard work and dedication to bringing the >>> llvm toolchain to FreeBSD. >>> >>> 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. >>> >>> Here's the logfile: >>> >>> http://jenkins.hardenedbsd.org:8180/jenkins/job/HardenedBSD-CURRENT-amd64/910/consoleText >>> >>> 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. > > I forgot to mention that WITH_LLD_IS_LD is set, too. I haven't tested > WITH_LLD_BOOTSTRAP && WITHOUT_LLD_IS_LD. Hi Shawn, I've tried reproducing, using WITH_LLD_BOOTSTRAP and WITH_LLD_IS_LD, but buildworld finishes without issues for me. This is with explicit __MAKE_CONF=/dev/null and SRCCONF=/dev/null environment variables, so everything else is at its defaults. Do you have any other particular settings, like modified default CFLAGS or LDFLAGS, either in your share/mk/*.mk files, or somewhere else? -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.1 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWXO2dQAKCRCwXqMKLiCW o9QJAKCH9QGkFX9OrN5rQX+HBPIayREQwgCfbT6ILIGDD79TPKSNXxqBeeonkho= =R08o -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79E2E246-88BA-4B0E-BCDA-570D4FA983E2>