devel/freebsd-gcc9 at powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang

[Gerald Pfeifer]

On Thu, 26 Dec 2019, Mark Millard wrote:
> I tried to build devel/freebsd-gcc9 at powerpc on a powerpc64 (in an
> ELFv1 clang environment) and it reported (listing just one of the
> examples that pointed to vec_step):

I maintain this is a bug in clang which should be address there.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239266

> It turns out that:
> 
> # ls -laT /usr/ports/devel/freebsd-gcc9/files/
> total 44
> drwxr-xr-x  2 root  wheel    512 Dec 25 19:25:26 2019 .
> drwxr-xr-x  3 root  wheel    512 Dec 25 19:25:26 2019 ..
> -rw-r--r--  1 root  wheel   4781 Dec 25 19:25:26 2019 patch-freebsd-format-extensions
> -rw-r--r--  1 root  wheel   1413 Dec 25 19:25:26 2019 patch-freebsd-libdir
> -rw-r--r--  1 root  wheel    588 Dec 25 19:25:26 2019 patch-gcc-configure
> -rw-r--r--  1 root  wheel  16346 Dec 25 19:25:26 2019 patch-gcc-freebsd-mips
> -rw-r--r--  1 root  wheel    231 Dec 25 19:25:26 2019 xtoolchain.mk.in
> 
> is missing the patch-clang-vec_step that is in:
> 
> FBSDG5L2# ls -laT /usr/ports/lang/gcc9/files/

That is a hack that can be used to work around the issue; I strongly
recommend addressing this in clang properly, though.

Gerald