Re: RELENG_10 to RELENG11 buildworld no possible ?
On 10 Jul 2019, at 15:27, Dimitry Andric wrote: > > On 9 Jul 2019, at 19:02, Warner Losh wrote: >> On Tue, Jul 9, 2019 at 12:12 AM Dimitry Andric wrote: >>> On 9 Jul 2019, at 08:08, Warner Losh wrote: > ... 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-compiler-version >>> says: >>> >>> Clang 3.5 >>> Apple Clang 6.0 >>> GCC 5.1 >>> Visual Studio 2017 >>> >> >> OK, so the clang in releng10 is 3.4.1. I'll update the note then. > > I committed a workaround in r349876, which makes it possible to directly > build clang 8.0.0 with clang 3.4.1, and will MFC that after the usual > timeout. I have now merged the workaround to stable/{11,12}, and reverted the notes, in r349967. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: RELENG_10 to RELENG11 buildworld no possible ?
On 9 Jul 2019, at 19:02, Warner Losh wrote: > On Tue, Jul 9, 2019 at 12:12 AM Dimitry Andric wrote: >> On 9 Jul 2019, at 08:08, Warner Losh wrote: ... >>> 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-compiler-version >> says: >> >> Clang 3.5 >> Apple Clang 6.0 >> GCC 5.1 >> Visual Studio 2017 >> > > OK, so the clang in releng10 is 3.4.1. I'll update the note then. I committed a workaround in r349876, which makes it possible to directly build clang 8.0.0 with clang 3.4.1, and will MFC that after the usual timeout. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: RELENG_10 to RELENG11 buildworld no possible ?
On Tue, Jul 9, 2019 at 12:12 AM Dimitry Andric wrote: > On 9 Jul 2019, at 08:08, Warner Losh wrote: > > > > On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote: > > On 8 Jul 2019, at 17:38, Warner Losh wrote: > > > > > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > > >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > > >>> Hi all, > > >>> > > Am 08.07.2019 um 08:30 schrieb Thomas Mueller >: > > 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 … > > >>> > > >>> Kind regards, > > >>> Patrick > > >> > > >> I am guessing all is good up until > > >> > > >> > > >> > https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > > >> > > >> 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. > > > > 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. > > > > 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. > > > > 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-compiler-version > says: > > Clang 3.5 > Apple Clang 6.0 > GCC 5.1 > Visual Studio 2017 > OK, so the clang in releng10 is 3.4.1. I'll update the note then. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_10 to RELENG11 buildworld no possible ?
On 9 Jul 2019, at 08:08, Warner Losh wrote: > > On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote: > On 8 Jul 2019, at 17:38, Warner Losh wrote: > > > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > >>> Hi all, > >>> > Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > 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 … > >>> > >>> Kind regards, > >>> Patrick > >> > >> I am guessing all is good up until > >> > >> > >> https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > >> > >> 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. > > 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. > > 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. > > 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-compiler-version says: Clang 3.5 Apple Clang 6.0 GCC 5.1 Visual Studio 2017 -Dimitry signature.asc Description: Message signed with OpenPGP
Re: RELENG_10 to RELENG11 buildworld no possible ?
On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote: > On 8 Jul 2019, at 17:38, Warner Losh wrote: > > > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > >>> Hi all, > >>> > Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > 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 … > >>> > >>> Kind regards, > >>> Patrick > >> > >> I am guessing all is good up until > >> > >> > >> > https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > >> > >> 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. > > 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. > > 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. > 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. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_10 to RELENG11 buildworld no possible ?
On 8 Jul 2019, at 17:38, Warner Losh wrote: > > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: >>> Hi all, >>> Am 08.07.2019 um 08:30 schrieb Thomas Mueller : 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 … >>> >>> Kind regards, >>> Patrick >> >> I am guessing all is good up until >> >> >> https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html >> >> 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. 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. 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. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: RELENG_10 to RELENG11 buildworld no possible ?
On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote: > On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > > Hi all, > > > >> Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > >> 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 … > > > > Kind regards, > > Patrick > > I am guessing all is good up until > > > https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html > > 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. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_10 to RELENG11 buildworld no possible ?
On 7/8/2019 3:09 AM, Patrick M. Hausen wrote: > Hi all, > >> Am 08.07.2019 um 08:30 schrieb Thomas Mueller : >> 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 … > > Kind regards, > Patrick I am guessing all is good up until https://lists.freebsd.org/pipermail/svn-src-stable-11/2019-April/009220.html 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. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_10 to RELENG11 buildworld no possible ?
Hi all, > Am 08.07.2019 um 08:30 schrieb Thomas Mueller : > 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 … Kind regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_10 to RELENG11 buildworld no possible ?
> On Sun, Jul 7, 2019, 8:23 PM Mike Tancsa wrote: > > Hi, > > I am trying to source update a RELENG_10 (stable) image to > > RELENG_11, but buildworld breaks. On another box, I can go to 11.2R, > > but dies with RELENG_11. I am guessing its not possible to build the > > latest clang from 10 thats in the latest RELENG11 version ? > Yes. I think that's right. You may need to go via 11.0. > Warner Or maybe via 11.2R, if that can be built from RELENG_10? Tom ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_10 to RELENG11 buildworld no possible ?
On Sun, Jul 7, 2019, 8:23 PM Mike Tancsa wrote: > Hi, > > I am trying to source update a RELENG_10 (stable) image to > RELENG_11, but buildworld breaks. On another box, I can go to 11.2R, > but dies with RELENG_11. I am guessing its not possible to build the > latest clang from 10 thats in the latest RELENG11 version ? > Yes. I think that's right. You may need to go via 11.0. Warner ===> lib/clang/libclang (all) > c++ -O2 -pipe -I/usr/obj/usr/src/tmp/usr/src/lib/clang/libclang > -I/usr/obj/usr/src/tmp/usr/src/lib/clang/libllvm > -I/usr/src/contrib/llvm/tools/clang/lib/Basic > -I/usr/src/contrib/llvm/tools/clang/lib/Driver > -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include > -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL > -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG > -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd11.3\" > -DLLVM_HOST_TRIPLE=\"i386-unknown-freebsd11.3\" > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -DLLVM_TARGET_ENABLE_AARCH64 > -DLLVM_TARGET_ENABLE_ARM -DLLVM_TARGET_ENABLE_MIPS > -DLLVM_TARGET_ENABLE_POWERPC -DLLVM_TARGET_ENABLE_SPARC > -DLLVM_TARGET_ENABLE_X86 > -DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser > -DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter > -DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler > -DLLVM_NATIVE_TARGET=LLVMInitializeX86Target > -DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo > -DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -ffunction-sections > -fdata-sections -MD -MF.depend.AST_APValue.o -MTAST/APValue.o > -Qunused-arguments -I/usr/obj/usr/src/tmp/legacy/usr/include -std=c++11 > -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -c > /usr/src/contrib/llvm/tools/clang/lib/AST/APValue.cpp -o AST/APValue.o > In file included from > /usr/src/contrib/llvm/tools/clang/lib/AST/APValue.cpp:15: > In file included from > /usr/src/contrib/llvm/tools/clang/include/clang/AST/ASTContext.h:19: > In file included from > /usr/src/contrib/llvm/tools/clang/include/clang/AST/ASTTypeTraits.h:20: > In file included from > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Decl.h:19: > In file included from > /usr/src/contrib/llvm/tools/clang/include/clang/AST/DeclBase.h:18: > In file included from > /usr/src/contrib/llvm/tools/clang/include/clang/AST/DeclarationName.h:17: > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1724:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(TypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1726:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(ArrayTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1728:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(AttributedTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1730:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(AutoTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1732:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(BuiltinTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1734:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(FunctionTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1736:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(ObjCObjectTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1738:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(ReferenceTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1740:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(TypeWithKeywordBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1742:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(ElaboratedTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1744:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(VectorTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1746:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(SubstTemplateTypeParmPackTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST/Type.h:1749:5: > error: anonymous union can only contain non-static data members > static_assert(sizeof(TemplateSpecializationTypeBitfields) <= 8, > ^ > /usr/src/contrib/llvm/tools/clang/include/clang/AST