32-bit powerpc system-clang based builds of devel/llvm40 and devel/llvm50: fails via "Host compiler appears to require libatomic, but cannot find it"

2017-12-05 Thread Mark Millard
[I experiment with system-clang based buildworld and/or buildkernel based TARGET_ARCH=powerpc64 and TARGET_ARCH=powerpc environments.] For TARGET_ARCH=powerpc devel/llvm40 and devel/llvm50 get failure reports like: -- Looking for __atomic_load_8 in atomic - not found CMake Error at cmake/modules/

[Bug 223776] ports-mgmt/pkg: lld confuses shared library tracking

2017-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223776 --- Comment #3 from Ed Maste --- This should be fixed in pkg 1.10.3 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list htt

Re: 32-bit powerpc system-clang based builds of devel/llvm40 and devel/llvm50: fails via "Host compiler appears to require libatomic, but cannot find it"

2017-12-05 Thread Roman Divacky
The cmake test just tries to compile: #include std::atomic x; int main() { return x; } What happens if you try to compile this small code with your host compiler? Roman On Tue, Dec 05, 2017 at 10:42:49AM -0800, Mark Millard wrote: > [I experiment with system-clang based > buildworld and/or b

Re: 32-bit powerpc system-clang based builds of devel/llvm40 and devel/llvm50: fails via "Host compiler appears to require libatomic, but cannot find it"

2017-12-05 Thread Mark Millard
On 2017-Dec-5, at 12:39 PM, Roman Divacky wrote: > The cmake test just tries to compile: > > #include > std::atomic x; > int main() { > return x; > } > > What happens if you try to compile this small code with your host compiler? > > Roman [I later show that it seems to be testing with: std

powerpc64 & system-clang vs. building the likes of lang/gcc7 (at least): vec_step name pollution causes compile failures, should gcc7 source code avoid the name?

2017-12-05 Thread Mark Millard
[I experiment with clang-based worlds and kernels on powerpc64 and powerpc. But I'm not sure that such is the only type of context is required to see the below problem.] Attempting to build lang/gcc7 on a system-clang based powerpc64 (world and kernel) gets: /wrkdirs/usr/ports/lang/gcc7/work/gcc