Opened 19 months ago
Last modified 19 months ago
#71824 new defect
gcc14-libcxx has a default setting of an old and useless compiler: clang17
| Reported by: | ballapete (Peter "Pete" Dyballa) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.10.5 |
| Keywords: | sonoma intel | Cc: | |
| Port: | gcc14-libcxx |
Description
root 244 /\ port variants gcc14-libcxx
gcc14-libcxx has the variants:
clang11: Build using the MacPorts clang 11 compiler
* conflicts with clang12 clang13 clang14 clang15 clang16 clang17 clang18 clang19
clang12: Build using the MacPorts clang 12 compiler
* conflicts with clang11 clang13 clang14 clang15 clang16 clang17 clang18 clang19
clang13: Build using the MacPorts clang 13 compiler
* conflicts with clang11 clang12 clang14 clang15 clang16 clang17 clang18 clang19
clang14: Build using the MacPorts clang 14 compiler
* conflicts with clang11 clang12 clang13 clang15 clang16 clang17 clang18 clang19
clang15: Build using the MacPorts clang 15 compiler
* conflicts with clang11 clang12 clang13 clang14 clang16 clang17 clang18 clang19
clang16: Build using the MacPorts clang 16 compiler
* conflicts with clang11 clang12 clang13 clang14 clang15 clang17 clang18 clang19
[+]clang17: Build using the MacPorts clang 17 compiler
* conflicts with clang11 clang12 clang13 clang14 clang15 clang16 clang18 clang19
clang18: Build using the MacPorts clang 18 compiler
* conflicts with clang11 clang12 clang13 clang14 clang15 clang16 clang17 clang19
clang19: Build using the MacPorts clang 19 compiler
* conflicts with clang11 clang12 clang13 clang14 clang15 clang16 clang17 clang18
Nothing else depends on clang17. So why do I need to support that compiler by keeping it on disk?
Note: See
TracTickets for help on using
tickets.

Feel free to choose a different variant?