On Sat, November 4, 2017 7:54 pm, Jeremie Courreges-Anglas wrote: > > Hi Tim, > > On Sat, Nov 04 2017, "trondd" <tro...@kagu-tsuchi.com> wrote: >> On Sat, November 4, 2017 3:13 pm, lan...@openbsd.org wrote: >>> bulk build on sparc64-1.ports.openbsd.org >>> started on Sun Oct 29 13:36:33 MDT 2017 >>> finished at Sat Nov 4 13:13:13 MDT 2017 >>> lasted 06D16h36m >>> done with kern.version=OpenBSD 6.2-current (GENERIC) #323: Sat Oct 28 >>> 21:27:53 MDT 2017 >>> >>> http://build-failures.rhaalovely.net//sparc64/2017-10-29/games/cataclysm-dda.log >>> >>> new failures >>> +failures/games/cataclysm-dda.log >>> >> >> Cataclysm won't build with base gcc because of missing -std=c++11 which >> is >> what seems to be happening here. >> >> I chose to configure the build for clang over gcc out of ports. >> >> Is there a quick flag to disable this on non-clang archs? Would anyone >> think I should make this work on gcc archs? Still wouldn't mean it will >> compile and run and I can't test it. > > I think that everybody should make an effort to support stuff on all > archs*. The transition to clang makes this a bit worse than before, but > people forget that they can test both clang and base gcc on their fast > amd64 machine. > > So nope, you can build it, and you can test it. ;)
Yes, I know I can test the different compilers, I already have. I was refering to your astrisk. :) Is 'COMPILER= gcc' the right way to fix this situation? It builds with base clang and devel/gcc/4.9. Thanks. Tim. > > * when it is doable, obviously; some ports are highly arch-dependent. > -- > jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 > E7EE >
