Date: Tue, 9 Jul 2019 08:12:32 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: Mike Tancsa <mike@sentex.net>, Thomas Mueller <mueller6722@twc.com>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: RELENG_10 to RELENG11 buildworld no possible ? Message-ID: <24F38383-0449-410D-82BF-A262D6073070@FreeBSD.org> In-Reply-To: <CANCZdfpZYU%2BZqNXbCCSfsJrPmU-1YHLg7HutWayma0wuQ4V3JQ@mail.gmail.com> References: <20b32c01-03a7-a376-a90f-7f5b8296181a@sentex.net> <CANCZdfqmaG38s8NFNk0snK4Ls3d76E9eQYySuT%2B-dzYaC66QRw@mail.gmail.com> <201907080637.x686bkG5071904@mailin1.pluspunkthosting.de> <46BA7C85-0BED-4797-98D7-1FC91E2C9EBE@punkt.de> <8ddc52ed-145e-6704-8e00-543b4ee91bff@sentex.net> <CANCZdfpfL80bpw-hz-fA4Ew1dCXRoL-L6ESOjgWh7MXnLb3D%2BA@mail.gmail.com> <C1695024-FC41-4B01-8363-12FBE2224C8D@FreeBSD.org> <CANCZdfpZYU%2BZqNXbCCSfsJrPmU-1YHLg7HutWayma0wuQ4V3JQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_20E29F33-76D2-4341-B19E-638CDEF68753 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 9 Jul 2019, at 08:08, Warner Losh <imp@bsdimp.com> wrote: >=20 > On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric <dim@freebsd.org> = wrote: > On 8 Jul 2019, at 17:38, Warner Losh <imp@bsdimp.com> wrote: > > > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa <mike@sentex.net> wrote: > >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > >>> Hi all, > >>> > >>>> Am 08.07.2019 um 08:30 schrieb Thomas Mueller = <mueller6722@twc.com>: > >>>> Or maybe via 11.2R, if that can be built from RELENG_10? > >>> I just completed a successful build of RELENG_11_2 on a > >>> RELENG_10_4 system =E2=80=A6 > >>> > >>> Kind regards, > >>> Patrick > >> > >> I am guessing all is good up until > >> > >> > >> = https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.ht= ml > >> > >> If I svn update -r346291(commit before the import of the new clang) = all > >> builds fine. > >> > >> Not sure if its worth a note in UPDATING, or mentioning it here in = the > >> google archives will be good enough for anyone else who runs into = it. > >> > > > > I think it is worth a note. I'll add one. > > > > We should also followup with dim@ to see why static_assert from = RELENG_10 > > is incompatible with the new compiler, and why it's used in a way = that > > would break. >=20 > I took a quick look, but I don't think there is any quick solution. = For > some reason, clang 3.4.1 (which shipped with 10.4) cannot handle the > static_asserts which are inside the piece of code in question. Also, > there are several other compilation errors, due to it being unable or > unwilling to cast pointers. >=20 > Upstream LLVM has recently bumped the requirements for building quite > aggressively, it could very well be that a higher version of clang or > gcc is now required to build 8.0, precisely because of the above. At > some point they apparently wanted to drop the workarounds for old > compilers. >=20 > Could you look into what the new requirement is? If there's no simple = workaround, I'd like to at least document what the minimum is better = than I have. Okay, = http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html#minimum-required-com= piler-version says: Clang 3.5 Apple Clang 6.0 GCC 5.1 Visual Studio 2017 -Dimitry --Apple-Mail=_20E29F33-76D2-4341-B19E-638CDEF68753 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCXSQwUAAKCRCwXqMKLiCW o67TAJ9MblqFpyx2fjLvjV6cisQ+epJqSwCgxkaSdwpi6bsbFAT3OyORnj8RN+k= =PNB0 -----END PGP SIGNATURE----- --Apple-Mail=_20E29F33-76D2-4341-B19E-638CDEF68753--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24F38383-0449-410D-82BF-A262D6073070>