[MacPorts] #63026: clang-12 does not build with analyzer

[MacPorts]

#63026: clang-12 does not build with analyzer
-----------------------+-----------------------------------
  Reporter:  szhorvat  |      Owner:  ken-cunningham-webuse
      Type:  defect    |     Status:  closed
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:  fixed     |   Keywords:
      Port:  clang-12  |
-----------------------+-----------------------------------

Comment (by mouse07410):

 > What is happening in your error is a parallel building issue that we
 have noticed in clang-12 and I have reported upstream. It seems to affect
 a small % of builds (it never happens to me, for example) but it does
 happen occasionally. I believe I know the cause.

 First, why does it not just pull the buldbot-created binary? I'd be
 perfectly happy to **not** recompile clang-12 locally.


 > This time, the arm64 builder hit this issue. I have already forced
 another build on it. We'll see if it builds next time (in a couple of
 hours). After all, the arm64 builder built it fine last last time.

 I'm having the same build failure when I disabled universal builds. :-(

 > Maybe upstream will fix the bug. I reported it on the llvm-mailing-list,
 so feel free to go add your voice to the "Me Too!" list if you like. I
 would open a bug report in their bug reported, but they are just about to
 shut that bug reported down forever, so .... no point.

 Yeah... Let's hope. Yes, I'll post to llvm-dev, maybe it would add some
 weight...

 > As always, we appreciate your support here. If you are in a terrible
 hurry and don't care to wait, you can temporarily set your build.jobs to 1
 in macports.conf, build it, and then delete the line

 Well... I like running the latest stable compilers, but not in that much
 of a hurry. Let me see, and probably try single-threaded build.

 > Would you say the better option would be to just stop parallel building
 for everyone, now that it's built on most of the buildbots anyway?

 No, probably not - if it builds OK for pretty much everybody else,
 **including build-bots**. To repeat myself - I don't really want to build
 it myself either! Macports for some reason does not pull the binaries and
 insists on doing local recompile, which I would prefer to avoid.

 > We can revisit this is in a few months when clang-13 comes out. Perhaps
 they will have fixed this issue by then.

 If I need to wait a few months for a working "latest" clang - so be it,
 it's not the end of the world. I'm using clang-11 now for most of my
 things...

 Will try the port again, and report here.

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