Opened 9 years ago
Closed 9 years ago
#46063 closed defect (invalid)
libgcc upgrade to 4.9.2_1 fails
Reported by: | dershow | Owned by: | larryv (Lawrence Velázquez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | mww@… | |
Port: | libgcc |
Description (last modified by mf2k (Frank Schima))
I have 4.9.2_0 on 10.9.5.
The attempt to update 10 4.9.2_1 fails. Log attached.
There are some tickets that are likely related, but it was suggested that a separate ticket be created.
See:
Attachments (1)
Change History (7)
comment:1 Changed 9 years ago by larryv (Lawrence Velázquez)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to larryv@… |
Status: | new → assigned |
comment:2 Changed 9 years ago by dershow
I suggested that they could be related because the fact that there are now four tickets in the last few days, all related to libgcc, that cause it to fail to upgrade or install. Clean log attached.
Changed 9 years ago by dershow
comment:3 Changed 9 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:4 Changed 9 years ago by larryv (Lawrence Velázquez)
The log contains many variations on this, as seen previously in #41095, #41643, #42076, #43282, and #43444:
:info:build clang: error: couldn't create cache file '/var/folders/4p/9fzq5t3s11sbl2g7mgjvzh280000gr/T/xcrun_db-3DK8BVlg' (errno=Permission denied)
Try deleting that directory and upgrading again.
% sudo rm -fR /var/folders/4p % sudo port clean libgcc % sudo port upgrade libgcc
comment:6 Changed 9 years ago by larryv (Lawrence Velázquez)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Great. We’ve seen that a few times but don’t really know why it happens or what’s to blame. Maybe it’s worth writing a FAQ about.
Do file more tickets in the future if you encounter issues using GCC. I plan to start revamping the GCC ports soon, and I’d like to know about problems early.
Replying to dersh@…:
There is no evidence that those tickets are related to this ticket or to each other. They involve different operating systems on different architectures, and every log I’ve seen exhibits a different failure mode. The only thing they have in common is that they involve GCC.
This log is still not clean.
Please clean
libgcc
, try upgrading again, and attach the newmain.log
.