[MacPorts] #63038: clang12: please re-enable the +analyzer as a default variant

[MacPorts]

#63038: clang12: please re-enable the +analyzer as a default variant
-------------------------+----------------------
  Reporter:  mouse07410  |      Owner:  kencu
      Type:  request     |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  clang-12    |
-------------------------+----------------------

Comment (by mouse07410):

 > I hear you, I hear you -- you like the analyzer. I was under the
 impression it never even worked properly

 It's not that static analyzer does not work - it occasionally produces
 false results. Sad, but still much better than nothing.

 > OK. Seems popular demand. For clang-12 v12.1.x, which is already tagged
 upstream, I will re-enable the analyzer, and everyone can just eat the
 PERL installation.

 Thank you! I' say, (a) the PERL cost is very easy to eat, and (b) PERL is
 already required for several ports, as far as I remember. So, no problem.

 > TBH I thought this was more of a "You moved my cheese!" thing, but I
 guess some actually use this.

 :-) :-)


 > Mouse -- I admit surprise that you would find a use for the static
 analyzer in a macport-clang-* installation, yet adding one line to a
 Portfile would be daunting

 Well, I'm fairly decent (and long-tooth experienced) with C/C++. I'm not
 experienced at all with the bowels of Macports. For example, I can't even
 locate the Portfile in the existing failed installation of clang-12
 (appears that it's not even there in the extracted source?!). I'm not
 saying that I can't be bothered to learn Macports, but it would take time
 I'd rather not invest right now, and probably useless in the long term -
 I'm not a maintainer of or contributor to any port. And I'm not itching to
 have a manually-maintained clone of Macports ports - one of the main
 reasons (for me) to use Macports instead of just compiling everything form
 sources is exactly the fact that Macports allows me to avoid messing with
 that stuff.

 > As I want to make sure we have your use case covered, can you point me
 to your example of how you use it, and I'll run some checks to make sure
 it works as promised?

 I'm a co-maintainer of Crypto++ library
 https://github.com/weidai11/cryptopp . Among other validation tools, It
 uses ASAN and UBSAN, like {{{make asan}}} and {{{make ubsan}}}. It would
 be nice if it worked with clang-12.

-- 
Ticket URL: <https://trac.macports.org/ticket/63038#comment:16>
MacPorts <https://www.macports.org/>
Ports system for macOS