Are macports builds prevented from accessing /dev/random ?
Sterling P. Smith
smithsp at fusion.gat.com
Tue Jun 13 20:59:51 UTC 2017
Is this trace mode?
----- Original Message -----
From: "Christopher Jones" <jonesc at hep.phy.cam.ac.uk>
To: "MacPorts Developers" <macports-dev at lists.macports.org>
Sent: Tuesday, June 13, 2017 1:57:57 PM
Subject: Are macports builds prevented from accessing /dev/random ?
I have a slightly odd issue… I am working on an update to the ROOT6 port, to the newly released 6.10.00 release,
As part of the build process their build system runs the root C++ interpreter on some example scripts, which generate various output files. This running of the script has part of the build process seems to be failing due to it being unable to access /dev/random…
The build step is
:info:build cd /opt/local/var/macports/build/_Users_chris_Projects_MacPorts_ports_science_root6/root6/work/build/tutorials && DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_Users_chris_Projects_MacPorts_ports_science_root6/root6/work/build/lib: ROOTIGNOREPREFIX=1 /opt/local/var/macports/build/_Users_chris_Projects_MacPorts_ports_science_root6/root6/work/build/bin/root.exe -l -q -b -n -x hsimple.C -e return
You don’t need to understand the details, just that root.exe is the main excitable and hsimple.C is a c++ source file that root interprets (using the cling interpreter built on top of the clang compiler).
This gives the error, when run inside a macports build
:info:build open('/dev/random'): Operation not permitted
Now, this works outside. So I suspect the build is in some way prevent the build process from accessing this. Is this possible ? If so, more to the point, is there a way I can get this to work… ?
More information about the macports-dev