Re: How to force using clang for a package?

[Benny Siegert <bsiegert%gmail.com@localhost>]

On Sun, 26 Dec 2021, Tobias Nygren wrote:

> It is wrong but there's currently no better way. We should maybe have
> CLANG_REQD like GCC_REQD. Base clang may or may not be sufficient
> depending on the package but we currently force pkgsrc clang regardless
> due to lack of infrastructure. It's easier to create the infrastructure
> after we have some example packages.

Too bad, but thanks for the explanation.

> Do you know the reason why the
> package requires clang?

It's a Rust package (wip/difftastic), and there is some vendored C++ code 
in there that spews tons of errors. For example:

warning: vendor/tree-sitter-haskell-src/scanner.cc:791:12: sorry, 
unimplemented: non-trivial designated initializers not supported
warning:      return [=](State & state) {
warning:             ^

For whatever reason (my C++ knowledge is not sufficient to understand 
what's wrong with this code and why), clang compiles it without 
complaints.

> Try this recipe:

Worked, thanks!

--
Benny