#67219 closed defect (worksforme)

clang-16 @16.0.1_1+analyzer: Cannot build

Reported by: thetrial (alabay) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: sierra legacy-os Cc:
Port: clang-16

Description

It began that clang-11 did not build. Though it is known that it should. I tried to directly jump to clang-16 with configure.compiler=macports-clang-9.0 – without jumping through several other clang-xy.

But … it did not work. And I don’t see what is the problem. I’ll attach the logfile.

Attachments (3)

main.log (9.0 MB) - added by thetrial (alabay) 19 months ago.
clang-16_main.log (118.0 KB) - added by thetrial (alabay) 19 months ago.
clang-11_main.log.7z (238.4 KB) - added by thetrial (alabay) 19 months ago.

Change History (8)

Changed 19 months ago by thetrial (alabay)

Attachment: main.log added

comment:1 Changed 19 months ago by ryandesign (Ryan Carsten Schmidt)

If the clang-16 port is programmed to use clang-11, then I would not bother trying to use an earlier clang to build it.

If you want to discuss why clang-11 isn't building for you, we can do that.

You could wait a couple days. By then we should have binaries of these clang ports available that you can install without having to compile them yourself.

comment:2 Changed 19 months ago by thetrial (alabay)

I tried the command sudo port install clang-16. That failed, too – with the annotations Error: Problem while installing clang-11 and Error: Unable to execute port: upgrade clang-14 failed. I’m not quite sure if I should open a new ticket or just add something to this one. I’ll attach both logfiles, one is zipped.

Last edited 19 months ago by thetrial (alabay) (previous) (diff)

Changed 19 months ago by thetrial (alabay)

Attachment: clang-16_main.log added

Changed 19 months ago by thetrial (alabay)

Attachment: clang-11_main.log.7z added

comment:3 Changed 19 months ago by kencu (Ken)

Upstream llvm has decided that a given version of clang should build with the clang two versions prior or newer, but not with older versions of clang than that.

They have similar requirements for libc++ building the current clang (two versions prior) but so far at least, that has not been so strict it appears. That shoe will drop, soon enough, though.

comment:4 Changed 19 months ago by thetrial (alabay)

Well, it all started with a simple upgrade outdated. And ended in an unawaited clang-struggle. clang-11 no, clang-16 no, and some other steps in between also no. I thougt I’d have clang-14 oder clang-15 onboard, but it seems I’ve (unintendently?) removed them. I tried a and not \(clang-11 \) … but macports insists on trying to install that. I could not catch that up with a clang-16. So I’m stuck again. Well. +analyzer+emulated_tls.darwin_16.x86_64 seems problematic. Whatever is hicking up now.

comment:5 Changed 19 months ago by cjones051073 (Chris Jones)

Resolution: worksforme
Status: newclosed

Latest version builds in buildbots for all platforms.

Note: See TracTickets for help on using tickets.