Opened 9 years ago
Closed 7 years ago
#49365 closed defect (worksforme)
"port upgrade outdated" for 2.3.4 fails in cmake
Reported by: | alexander.tudor@… | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | mojca (Mojca Miklavec) | |
Port: | cmake |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi,
I tried to update from 2.3.3 to 2.3.4 and failed as above. My Mac runs 10.9.5 with Xcode 6.1.1. The upgrade fails on cmake with:
... Error: org.macports.configure for port cmake returned: configure failure: command execution failed ...
Thoughts?
Thank you,
Alex
Attachments (1)
Change History (7)
comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
Changed 9 years ago by maqdev@…
comment:3 follow-up: 6 Changed 9 years ago by mojca (Mojca Miklavec)
Owner: | changed from macports-tickets@… to michaelld@… |
---|
I would suspect that maqdev's problem is different from Alexander's (one is failing during configure, the other one during build), but there's no way to diagnose Alexander's problem without the log anyway.
Is -framework libcurl
expected? maqdev, do you have a curl framework installed under /usr/local
or somewhere in your local frameworks?
comment:5 Changed 9 years ago by michaelld (Michael Dickens)
Please do:
sudo port clean "cmake*" sudo port selfupdate sudo port upgrade outdated
and, hopefully this will take care of your issues. I fixed the "non-MacPorts Curl and other related dependencies" issue already. I don't know about the configure issue since there's no log but I did just updated cmake to 3.4.1 so maybe it takes care of this issue.
Please report back success of failure. If the latter, please attach a log.
comment:6 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Replying to mojca:
I would suspect that maqdev's problem is different from Alexander's (one is failing during configure, the other one during build), but there's no way to diagnose Alexander's problem without the log anyway.
Closing, since no log was provided.
Is
-framework libcurl
expected? maqdev, do you have a curl framework installed under/usr/local
or somewhere in your local frameworks?
That's #49696.
Please attach the main.log file. It's impossible for us to know what the problem was without seeing the log.