Opened 5 days ago
Last modified 13 hours ago
#71269 assigned defect
valgrind-macos-devel @3.22.0-r2023-10-29: configure: error: Valgrind works on Darwin 10.x-23.x (Mac OS X 10.6-10.11 and macOS 10.12-14.0)
Reported by: | gautham81928 | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.10.4 |
Keywords: | sequoia | Cc: | |
Port: | valgrind-macos-devel |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
It gave an error:
Failed to configure valgrind-macos-devel: configure failure: command execution failed.
How do I fix this error?
Attachments (1)
Change History (7)
comment:1 Changed 5 days ago by reneeotten (Renee Otten)
Port: | valgrind-macos-devel added |
---|---|
Summary: | valgrind-macos-devel failed to configure → valgrind-macos-devel: failed to configure |
Changed 5 days ago by gautham81928
comment:3 Changed 5 days ago by reneeotten (Renee Otten)
Owner: | set to raimue |
---|---|
Status: | new → assigned |
the log says
:info:configure configure: error: Valgrind works on Darwin 10.x-23.x (Mac OS X 10.6-10.11 and macOS 10.12-14.0
so if there is an newer upstream version that is likely worth updating to.
comment:4 Changed 5 days ago by gautham81928
I am currently running Mac OS 15. So is there anything for this version of Mac?
comment:5 Changed 4 days ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | sequoia added |
Summary: | valgrind-macos-devel: failed to configure → valgrind-macos-devel @3.22.0-r2023-10-29: configure: error: Valgrind works on Darwin 10.x-23.x (Mac OS X 10.6-10.11 and macOS 10.12-14.0) |
Version: | → 2.10.4 |
Yes, macOS 15 support was allegedly added to the upstream valgrind-macos project two months ago, so Renee's suggestion that the maintainer of this port should update it does have a chance of making the port work on macOS 15.
comment:6 Changed 13 hours ago by gautham81928
It seems that I have an ARM based Mac, and they do not have support for that. Are there any alternatives?
Note: See
TracTickets for help on using
tickets.
please attach the
main.log
file to this ticket, otherwise nobody has any idea what possibly could have gone wrong.