Opened 4 years ago
Closed 4 years ago
#60918 closed defect (fixed)
cppzmq @4.6.0_0: Error: Failed to configure cppzmq
Reported by: | brislawn | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.3 |
Keywords: | Cc: | ||
Port: | cppzmq |
Description
Looks like possibly a cmake problem; logfile attached. This makes no sense since I apparently already have the latest version activated:
bash-3.2# port upgrade outdated ---> Computing dependencies for cppzmq ---> Configuring cppzmq Error: Failed to configure cppzmq: configure failure: command execution failed Error: See /opt/macports/var/macports/logs/_opt_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cppzmq/cppzmq/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. bash-3.2# port installed cmake The following ports are currently installed: cmake @3.18.0_1+docs+python37 (active) bash-3.2# port installed cppzmq The following ports are currently installed: cppzmq @4.6.0_0 (active)
Appreciate any insights anyone can offer. Thanks,
-Chris Brislawn
Attachments (2)
Change History (13)
Changed 4 years ago by brislawn
comment:1 Changed 4 years ago by michaelld (Michael Dickens)
comment:2 Changed 4 years ago by michaelld (Michael Dickens)
BTW> my log is from doing "sudo port build cppzmq" when the same cppzmq was installed and active ... it should work, if a compiler is found ...
comment:3 Changed 4 years ago by michaelld (Michael Dickens)
Maybe try reinstalling the Xcode commandline tools? < https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt >
comment:4 Changed 4 years ago by michaelld (Michael Dickens)
Owner: | set to michaelld |
---|---|
Status: | new → assigned |
comment:5 Changed 4 years ago by brislawn
No banana.
Background: I upgraded to OSX 10.15.6 recently and upgraded XCode to 11.6 using the Software Update tool. When I then tried to run the usual xcode-select --install, I got a message saying that the command line tools were *already* installed. The port command hasn't complained about the command line tools since the upgrade, so I figured they had survived the OS upgrade (as had the previous version of XCode).
On your advice I downloaded CLT 11.5 (the latest stable release) from developer.apple.com and installed it successfully. Software Update now says I can upgrade to CLT beta 3 for XCode 12.0, but I haven't done that (yet) since it makes me nervous. Now when I clean cppzmq and upgrade outdated the configure log for cppzmq looks like yours, then it crashes on the same cmake error as before.
The new logfile (attached) is now much shorter than before, however. The :info:configure text you quoted was present previously, but earlier on in the logfile. Now that text appears at the end of the (shorter) logfile. Followed by a cmake error.
Thoughts?
Thanks,
-Chris
bash-3.2# port upgrade outdated ---> Computing dependencies for cppzmq ---> Fetching distfiles for cppzmq ---> Verifying checksums for cppzmq ---> Extracting cppzmq ---> Configuring cppzmq Error: Failed to configure cppzmq: configure failure: command execution failed Error: See /opt/macports/var/macports/logs/_opt_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cppzmq/cppzmq/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. bash-3.2# port installed cppzmq The following ports are currently installed: cppzmq @4.6.0_0 (active)
comment:6 Changed 4 years ago by michaelld (Michael Dickens)
OK ... so I did some traceback and what I'll do is disable testing by default. That should solve the issue here. I can always enable testing for my specific install.
comment:7 Changed 4 years ago by michaelld (Michael Dickens)
comment:8 Changed 4 years ago by michaelld (Michael Dickens)
Please do a "sync" or "selfupdate" and then "clean cppzmq" and then try again. Hopefully this time it will work.
comment:9 Changed 4 years ago by michaelld (Michael Dickens)
Just FYI that I'm pretty sure the issue really was that CMake was not able to download the "Catch" project, and hence the CMake commands provided by it were not available. Probably be a networking issue on your end ... maybe a firewall that isn't allowing the download, or some system setting that's blocking the download ... I really don't know. Since we don't actually use the testing for anything, my tweak here just disables it, which in turn should both disable this spurious download as well as speed up the install.
comment:10 Changed 4 years ago by brislawn
Looks like it's working now. I did a port selfupdate and
bash-3.2# port clean cppzmq ---> Cleaning cppzmq bash-3.2# port upgrade outdated ---> Computing dependencies for cppzmq ---> Fetching distfiles for cppzmq ---> Verifying checksums for cppzmq ---> Extracting cppzmq ---> Configuring cppzmq ---> Building cppzmq ---> Staging cppzmq into destroot ---> Installing cppzmq @4.6.0_1 ---> Cleaning cppzmq ---> Computing dependencies for cppzmq ---> Deactivating cppzmq @4.6.0_0 ---> Cleaning cppzmq ---> Activating cppzmq @4.6.0_1 ---> Cleaning cppzmq ---> Computing dependencies for py37-urllib3 ...
Thanks for your quick help with this! You can close the ticket on it.
As for the ultimate (cmake?) source of the problem, while I am indeed running macports port through a VPN tunnel to my firewalled office network (because that's how my macports proxy settings are configured), I was able to install cppzmq from that same network some months back as part of a gnuradio 3.7 installation. I just don't understand why macports was trying to *reinstall* cppzmq even though cppzmq @4.6.0_0 was already active in my setup (I'm installing these ports on a MBP).
Now I get to see whether I can upgrade to gnuradio 3.8....
Thanks again,
-Chris
comment:11 Changed 4 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I'm glad that works! You'll note that this port is now cppzmq @4.6.0_1
, not cppzmq @4.6.0_0
... so, there's been a rev-bump since you last installed it ... I think this was to make sure to use a C++11 compliant compiler ... which might not be needed now ... hmmm ... anyway, I'll close out this ticket & I hope your GR install goes smoothly!
Very odd ... the configure log should look more like:
In your log, it's just
Maybe the Xcode commandline tools are not installed correctly?