[MacPorts] #55705: adding new clang compilers:: why so painful?
MacPorts
noreply at macports.org
Tue Jan 16 21:40:07 UTC 2018
#55705: adding new clang compilers:: why so painful?
-----------------------------------+----------------------
Reporter: gaming-hacker | Owner:
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.4.2
Keywords: compiler, environment | Port: macports
-----------------------------------+----------------------
hello,
i always use the latest clang compiler and switched to clang-6.0 so i need
to rebuilt a lot of ports because i don't keep old compilers around. many
ports do not handle new compilers, here is an example, there are other
ports like this.
port: ld64-latest
...
set all_llvm_variants {llvm39 llvm40 llvm50 llvmdev}
array set llvm_variant_version {llvm33 3.3 llvm34 3.4 llvm37 3.7 llvm39
3.9 llvm40 4.0 llvm50 5.0 llvmdev devel}
...
so i manually updated these to
set all_llvm_variants {llvm39 llvm40 llvm50 llvm60 llvmdev}
array set llvm_variant_version {llvm33 3.3 llvm34 3.4 llvm37 3.7 llvm39
3.9 llvm40 4.0 llvm50 5.0 llvm60 6.0 llvmdev devel}
Are ports better ways to 'fix' these ports without having to manually
update them?
Thanks
--
Ticket URL: <https://trac.macports.org/ticket/55705>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list