Open jrabinow opened 1 year ago
it looks like libproc is failing to build here w/ fatal error: 'libproc.h' file not found
.
This seems to be the same error as https://github.com/andrewdavidmackenzie/libproc-rs/issues/82 .
I just built successfully on my OSX system, but I'm still on Catalina (and on an intel based machine).
Thanks for linking both issues, I reported my issue upstream along with a patch. I'm not sure how long it'll take to fix or what functionality is included in the libproc library - asking with zero context here, does it make sense to try to remove the dependency on libproc-rs? If not, it might make sense to close this issue since it looks like the problem is upstream
does it make sense to try to remove the dependency on libproc-rs?
py-spy isn't actually using libproc directly, libproc is being used by the remoteprocess
and proc-maps
dependencies of py-spy. the remoteprocess dependency is using it to get the exe/cwd https://github.com/benfred/remoteprocess/blob/70509587992eead0fdeb5534125c8ac7db2ce9a8/src/osx/mod.rs#L50-L62 - and proc-maps is using it to get the filename for a region of memory https://github.com/rbspy/proc-maps/blob/6d6fcb987fe663a7232b90a4182feb0dfc7c1f4c/src/mac_maps/mod.rs#L146 .
We could replace it in both cases, but ideally we'd just get it fixed upstream.
Both libproc-rs and proc-maps have released new versions with the fix
Hi @benfred would it be possible to release a new version of py-spy including the upstream fix from libproc-rs
?
I'm trying to build py-spy to add it to MacPorts, but I seem to be running into an issue with libproc. Machine info:
When attempting to
cargo install
, I get the following error:My attempt at a macports port seems to be running into an issue with libproc as well: macports_build.txt
Any ideas on how I could get
py-spy
to build?