Opened 14 months ago

Closed 14 months ago

Last modified 14 months ago

#59243 closed defect (worksforme)

clang-9.0 dependency error in macOS 10.15

Reported by: jerryzj (Jerry ZJ) Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.6.1
Keywords: Cc: larryv (Lawrence Velázquez)
Port: clang-9.0


When I tried to install clang-9.0 after llvm-9.0 installed.

The dependency list shows that it needs llvm-8.0, I think this might be a bug.

Attachments (1)

截圖 2019-10-10 19.53.11.png (306.8 KB) - added by jerryzj (Jerry ZJ) 14 months ago.
screenshot of this error

Download all attachments as: .zip

Change History (10)

Changed 14 months ago by jerryzj (Jerry ZJ)

screenshot of this error

comment:1 Changed 14 months ago by mf2k (Frank Schima)

Milestone: MacPorts 2.7.0
Priority: HighNormal

The Priority and Milestone fields are for use by Macports team members only.

comment:2 Changed 14 months ago by mf2k (Frank Schima)

Cc: larryv added
Keywords: bug removed
Owner: changed from <jeremyhu@…> to jeremyhu

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

I think cctools is calling it in.

You can find out with port rdeps clang-9.0

We should not be making people install cctools or ld64 on Catalina (or Mojave or High Sierra). If we do ask them to install it, then it should be the +xcode variant of them, which is a no-op. I have to talk to Jeremy about this at some point

comment:4 Changed 14 months ago by jerryzj (Jerry ZJ)

kencu, thanks, I see.

But my question is, why do we need cctools? Before we installing MacPorts, we already have ar, as and ld installed...

I think this dependency requirement is nonsense.

comment:5 Changed 14 months ago by kencu (Ken)

that's part 2 of what I said above. You're right, there is no real need for it today. However, the Apple engineer who maintains cctools and ld64 has traditionally made sure they are the very latest versions on all os versions, so it's been a good thing overall throughout MacPorts history.

comment:6 Changed 14 months ago by jerryzj (Jerry ZJ)

Yeah, but in my experience (build clang+llvm 9.0 on Linux), we only need CMake, gcc(based on the release, it can be 7 to 9) and python to build it. I think MacPorts make things too complicated :(

BTW, if I already have CMake installed, why MacPorts still build its own CMake in /opt/local/bin I don't really understand the logic behind this approach...

Last edited 14 months ago by jerryzj (Jerry ZJ) (previous) (diff)

comment:7 Changed 14 months ago by kencu (Ken)

reproducible builds. It's a very valid concept we try to aim for.

MacPorts can't know what cmake you have, or how it's exactly installed and configured, unless we use ours.

Same for all the other tools.

But for new os versions with current Xcodes, we might need to make an exception for cctools and ld64...

Last edited 14 months ago by kencu (Ken) (previous) (diff)

comment:8 Changed 14 months ago by jerryzj (Jerry ZJ)

I just modified the port file (remove redundant dependencies), and start building clang-9.0 now. Hope that works...

comment:9 Changed 14 months ago by kencu (Ken)

Resolution: worksforme
Status: assignedclosed

you are free to do that! I do it myself all the time. But as I'm sure you'll understand, we can only handle tickets based on our stock setup.

Thanks for using MacPorts, and we welcome any future contributions you might care to make!

I'll close this now, as "expected behavior" although your points are noteworthy and appreciated.

(I have to stop typing on this ipad, or people will think I ca't spel!

Last edited 14 months ago by kencu (Ken) (previous) (diff)
Note: See TracTickets for help on using tickets.