Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

For 11.0 -r300904 using devel/powerpc64-gcc on powerpc64 (not building clang) I get the failures: > --- all_subdir_usr.bin --- . . . (some warnings) . . . > stdarg.h(40): syntax error [249] > stdarg.h(98): syntax error [249] > llib-lposix(307): syntax error [249] > llib-lposix(308): syntax error

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

I'll update to 11.0 -r300904 to pick up the external toolchain fix for -r300886's problem. > CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc TARGET_ARCH=powerpc64 \ >__MAKE_CONF=/dev/null SRCCONF=/dev/null make buildworld The above likely would have problems with finding files in

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

On 28 May 2016, at 06:18, Mark Millard wrote: ... > The -r300886 powerpc64 devel/powerpc64-gcc combination with no clang build > included has failed: > > --- all_subdir_usr.bin --- > endian.h(111): warning: bitwise operation on signed value possibly > nonportable [117] >

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

On 2016-May-27, at 6:04 PM, Mark Millard wrote: > [Top posting failure results again.] > > -r300886 for powerpc64 failed for each of: > > /usr/src/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/lib/Analysis/AnalysisDeclContext.cpp > >

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

[Top posting failure results again.] -r300886 for powerpc64 failed for each of: /usr/src/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/lib/Analysis/AnalysisDeclContext.cpp /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/ARCMT.cpp with the

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

[I'm top posting the results of the failed build.] It looks like the following has been addresses in -r300884. libcompat also got a -isystem in -r300885. -r300886 did "Move external GCC compiler hacks to bsd.sys.mk". So I'll retry based on -r300886. Failure details. . . Both the powerpc64

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

On 2016-May-27, at 1:50 PM, Dimitry Andric wrote: > > On 27 May 2016, at 01:53, Mark Millard wrote: >> >> I do buildworld/buildkernel on a powerpc64 targeting itself via >> lang/powerpc64-xtoolchain-gcc (a.k.a. lang/powerpc64-gcc for the most part). >> [Getting that lang/powerpc64-gcc

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

On 27 May 2016, at 01:53, Mark Millard wrote: > > I do buildworld/buildkernel on a powerpc64 targeting itself via > lang/powerpc64-xtoolchain-gcc (a.k.a. lang/powerpc64-gcc for the most part). > [Getting that lang/powerpc64-gcc installed for self-hosted use does take some

11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

I do buildworld/buildkernel on a powerpc64 targeting itself via lang/powerpc64-xtoolchain-gcc (a.k.a. lang/powerpc64-gcc for the most part). [Getting that lang/powerpc64-gcc installed for self-hosted use does take some work-around activity.] I have buildworld build clang (but not use it). [I've