You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so upon trying to build from source (latest version on github) on a Mac OS (Latest version at time of writing) device ive encountered no end of problems trying to get sipp to work with sippy_cup, after installing the homebrew version of sipp with pcap flags enabled to fix the issue sippy_cup was displaying, sippy_cup now agnowledges the pcap libs are present but now gives the pollowing error message.
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/bundler_version_finder.rb:80:in `pwd': Operation not permitted - getcwd (Errno::EPERM)
plus 10 more lines of the same,
now to me this seemed like a perssions error to me so tried to run as root and still gave the same errors.
very possible ive got something simple round the wrong way or maybe an issue with newer versions of Mac OS ?
The text was updated successfully, but these errors were encountered:
so upon trying to build from source (latest version on github) on a Mac OS (Latest version at time of writing) device ive encountered no end of problems trying to get sipp to work with sippy_cup, after installing the homebrew version of sipp with pcap flags enabled to fix the issue sippy_cup was displaying, sippy_cup now agnowledges the pcap libs are present but now gives the pollowing error message.
plus 10 more lines of the same,
now to me this seemed like a perssions error to me so tried to run as root and still gave the same errors.
very possible ive got something simple round the wrong way or maybe an issue with newer versions of Mac OS ?
The text was updated successfully, but these errors were encountered: