Ticket #19626 (closed defect: fixed)
ccache port doesn't set itself up as gcc-4.2
| Reported by: | bzbarsky@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Port: | ccache |
Description (last modified by macsforever2000@…) (diff)
The portfile for ccache has the following:
foreach {bin} {
cc
gcc gcc2 gcc3 gcc-3.3 gcc-4.0
c++ c++3 c++-3.3 c++-4.0
g++ g++2 g++3 g++-3.3 g++-4.0
} {
ln -sf ${prefix}/bin/ccache ${destroot}${symlinks_dir}/${bin}
}
At least on Leopard, it should also set up gcc-4.2 and g++-4.2.
Attachments
Change History
comment:1 Changed 4 years ago by macsforever2000@…
- Owner changed from macports-tickets@… to nox@…
- Description modified (diff)
comment:2 follow-up: ↓ 5 Changed 3 years ago by nox@…
- Status changed from new to closed
- Resolution set to wontfix
r64755, those symlinks are too much of a bother to maintain.
comment:3 Changed 3 years ago by bzbarsky@…
So wait. Doesn't this make ccache not work correctly out of the box? Shouldn't there be at least some indication when one tries to run "ccache" or something that it needs more setup?
comment:4 Changed 3 years ago by landonf@…
- Status changed from closed to reopened
- Resolution wontfix deleted
This forces all ccache users to individually set up symlinks rather than work out of the box. New compiler versions are not released very often. I'd really like to re-integrate the symlink code, which was in place for 8 years (2002 through 2010) and relied on by users (including myself).
comment:5 in reply to: ↑ 2 Changed 3 years ago by dstwo@…
Replying to nox@…:
r64755, those symlinks are too much of a bother to maintain.
I agree with the other posters. Removing the symlinks from the setup code makes no sense.
I just "upgrade" ccache, and suddenly it stops working with no explanation? WTF. There should be at the minimum documentation to explain how to set up ccache correctly.

