Opened 14 years ago
Closed 13 years ago
#29171 closed defect (fixed)
MacPorts clang shouldn't override system clang
| Reported by: | howarth@… | Owned by: | mfeiri |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | lang | Cc: | jeremyhu (Jeremy Huddleston Sequoia) |
| Port: | clang |
Description
The clang package currently overrides the system clang. The installed MacPorts clang executable should be renamed as mp-clang so as to not block the proper usage of Apple's clang.
Change History (3)
comment:1 Changed 14 years ago by mfeiri
| Owner: | changed from macports-tickets@… to mfeiri@… |
|---|---|
| Status: | new → assigned |
comment:2 Changed 13 years ago by jmroot (Joshua Root)
| Cc: | jeremyhu@… added |
|---|
This is fixed by the versioned clang ports, right?
comment:3 Changed 13 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Yes. And you can use 'port select clang ...' to choose the default one as well
Note: See
TracTickets for help on using
tickets.
This was not an issue before the release of Xcode 4.0 but I agree that the new situation is not optimal. I previously tried to use "--program-suffix=-mp" in configure.args like we do in the gcc Portfiles, but this flags seems to get ignored by the clang build system. For now I can just rename the binaries in a post-destroot phase. To stay in line with our gcc compilers I'd prefer clang-mp and clang++-mp.