Re: userland build failure in libgomp

2020-01-16 Thread Riccardo Mottola
Hi, Robert Swindells wrote: could it be that the combination MKLLVM = no HAVE_LLVM=no MKLLVMRT = no is not supported? You could test this by building without those options, you should get a gcc toolchain. I use MKLLVMRT=no for several architectures and did a full build a couple of days ago.

Re: userland build failure in libgomp

2020-01-14 Thread Robert Swindells
Riccardo Mottola wrote: >I confirm the peristent build failure, even if starting totally from >scratch (clean obj dir) and no -u flag. >Built tools first, then distribution. Same error, on amd64 > >could it be that the combination >MKLLVM = no >HAVE_LLVM=no >MKLLVMRT = no > >is not supported?

Re: userland build failure in libgomp

2020-01-14 Thread Riccardo Mottola
Hi all! I confirm the peristent build failure, even if starting totally from scratch (clean obj dir) and no -u flag. Built tools first, then distribution. Same error, on amd64 could it be that the combination MKLLVM = no HAVE_LLVM=no MKLLVMRT = no is not supported? the error is: #

Re: userland build failure in libgomp

2020-01-14 Thread Riccardo Mottola
Hi List! Yesterday, I did a new CVS update. I did rebuild tools and userland. I ad mit, to save some time, I used the "-u" update flag. The issue came up again however. I will try today again, without an update build. Riccardo Riccardo Mottola wrote: #   compile  libgomp/oacc-init.o