On Mon, Dec 25, 2017 at 06:49:15AM +0100, Jeremie Courreges-Anglas wrote:
>
> Have you tried a build with COMPILER = ports-clang?
I have tried it on sparc64 and it doesn't work, but this is not an
issue with the port.
I get these errors:
In file included from
/usr/ports/pobj/witchblast-0.7.5/witchblast-0.7.5/src/WitchBlastGame.cpp:17:
In file included from
/usr/ports/pobj/witchblast-0.7.5/witchblast-0.7.5/src/WitchBlastGame.h:32:
In file included from /usr/local/include/c++/4.9.4/thread:40:
In file included from /usr/local/include/c++/4.9.4/memory:82:
In file included from /usr/local/include/c++/4.9.4/bits/shared_ptr.h:52:
/usr/local/include/c++/4.9.4/bits/shared_ptr_base.h:157:10: error: unexpected
token
_GLIBCXX_WRITE_MEM_BARRIER;
^
/usr/local/include/c++/4.9.4/sparc64-unknown-openbsd6.2/bits/atomic_word.h:40:21:
note: expanded from macro '_GLIBCXX_WRITE_MEM_BARRIER'
__asm __volatile ("membar #StoreStore":::"memory")
^
<inline asm>:1:9: note: instantiated into assembly here
membar #StoreStore
^
258 warnings and 12 errors generated.
I get these on some other ports too. It's not something I'm personally
doing wrong, since these kinds of errors appear in bulk builds:
http://build-failures.rhaalovely.net//sparc64/2017-12-03/games/easyrpg.log
http://build-failures.rhaalovely.net//sparc64/2017-12-03/games/hyperrogue.log
http://build-failures.rhaalovely.net//sparc64/2017-12-03/devel/dlib.log
http://build-failures.rhaalovely.net//sparc64/2017-12-03/x11/worker.log
etc
Anyone have any idea what's going on here? Some of these ports build
just fine with ports-gcc, including witchblast.
Witchblast doesn't just build, it also runs well on sparc64 compiled
with ports-gcc (I played it for a bit), so the port itself isn't
broken, something is wonky with clang, or the headers, or something
else.
--
Kaashif Hymabaccus
GPG: 3E810B04
