Sandboxing in Macports does not work correctly on 10.6.x: sh: /bin/ps: Operation not permitted

[barracuda156]

I see this regularly. Specific example is from CMake build on 10.6.8 x86_64 (Xcode 4.2):

-- Looking for a Fortran compiler
-- Looking for a Fortran compiler - NOTFOUND
sh: /bin/ps: Operation not permitted

It also happens in Rosetta and on 10.6 PPC.

In a few cases it created a trouble and I needed to add a hack to a portfile. In most cases it does not seem to have consequences or they are not evident. Should we do something about it?

[kencu (Ken)]

This spurious message has nothing to do with SnowLeopard, Rosetta, or PPC specifically. It is seen on all systems, only on MacPorts I believe, and only when using cmake, or building cmake as far as I can tell.

There are many tickets where this message is mentioned, going back at least 10 years, and the response back from Clemens and others is always to "ignore it" and look for the real problem. Indeed, the real issue causing the build failure is always something else, and this warning is never the actual problem.

sh: /bin/ps: Operation not permitted

After 10 years, if it was simple to make this messge not happen, I presume someone would have done that. I am not personally exactly sure why that is the message that shows up for other build failures, but I can tell you the issue to be fixed is always something else, not what that message says.

[barracuda156]

Replying to kencu:

This spurious message has nothing to do with SnowLeopard, Rosetta, or PPC specifically. It is seen on all systems, only on MacPorts I believe, and only when using cmake, or building cmake as far as I can tell.

There are many tickets where this message is mentioned, going back at least 10 years, and the response back from Clemens and others is always to "ignore it" and look for the real problem. Indeed, the real issue causing the build failure is always something else, and this warning is never the actual problem.

sh: /bin/ps: Operation not permitted

After 10 years, if it was simple to make this messge not happen, I presume someone would have done that. I am not personally exactly sure why that is the message that shows up for other build failures, but I can tell you the issue to be fixed is always something else, not what that message says.

Thank you for clarification. Interesting.