Re: bazel 4.2 and 3.7 no longer building with native clang

On 14/07/2022 12:23 pm, Steven Smith wrote: I've conceded defeat to bazel. I've lost interest in the battle but I wish you luck if you wish to take it up... My interest in bazel is the minimum necessary to get tensorflow-related projects working. That was also my starting point.

Re: bazel 4.2 and 3.7 no longer building with native clang

> I've conceded defeat to bazel. I've lost interest in the battle but I wish > you luck if you wish to take it up... My interest in bazel is the minimum necessary to get tensorflow-related projects working. FWIW, bazel 5 builds and works on macOS, but previous versions do not, and I strongly

Re: bazel 4.2 and 3.7 no longer building with native clang

Hi On 13/07/2022 10:50 pm, Ryan Schmidt wrote: On Jul 13, 2022, at 11:46, Steven Smith wrote: How does one reconfigure the bazel Portfile to use a previous version of clang that has a chance of working to build previous versions of bazel, which are in turn necessary to build the tensor flow

Re: bazel 4.2 and 3.7 no longer building with native clang

On Jul 13, 2022, at 11:46, Steven Smith wrote: > How does one reconfigure the bazel Portfile to use a previous version of > clang that has a chance of working to build previous versions of bazel, which > are in turn necessary to build the tensor flow packages. If certain compilers that

bazel 4.2 and 3.7 no longer building with native clang

I’m trying to update a bunch of tensorflow packages, but am getting hung up on bazel issues (see https://trac.macports.org/ticket/64442 ). I have a fix for this issue, but am unable to build either bazel 4.2 or 3.7 with the native /usr/bin/clang