Antoine Jacoutot <ajacou...@bsdfrog.org> wrote: > On Mon, Apr 13, 2020 at 08:13:50PM -0400, Brad Smith wrote: > > On 4/13/2020 5:26 PM, Antoine Jacoutot wrote: > > > > > On Mon, Apr 13, 2020 at 12:47:47PM -0400, Kurt Mosiejczuk wrote: > > > > Two things cause the build to fail on sparc64: "-Werror" and the need > > > > for C99. > > > > > > > > There are a bunch of deprecated functions that throw warnings and > > > > -Werror > > > > aborts the build, so there is a patch to remove that from meson.build. > > > > > > > > The C99 is fixed by adding -std=gnu99 to CFLAGS. > > > > > > > > This patch fixes the build on sparc64 (And presumably other base-gcc > > > > arches). > > > Can you put the same comment in the patch please. > > > So that I can remove all these tweaks once sparc64 moves to llvm. > > > > > > But there are more archs than just sparc64 which are !clang archs. > > That can run that kind of software?
The schism of clangs vs gcc is becoming more narrow. The remaining gcc architectures are challenged in other ways. I hope this is making ports decisions easier. We hope to cross clang after 6.7, if a few issues which need handling are looked at by our experts. That's not certain, I'm only hoping. The sparc64 clang issues are much smaller than few months ago.
