I have a software for about 4 years which recently a user reported that he was having issues with the relative path. The main script that he has the issue is this file. I suspect that the problem lies at these lines.
In response, I proposed using the FindBin module modifying it to this instead. This would ensure that no matter from where he runs the main script, the relative paths would be fixed to the position of the running script but not cwd. (Here is a video I did for him in response)
However this has not solved his issues. Any body else is having any idea?
Did you try using Cwd? like
use Cwd;
Cwd::realpath($0) =>gives absoulute path of current dir
P.S: I don't know Perl. I've asked my friend and he suggested this.
Ron
Thinker
assuming there is no error from perl side at line 904 , and the interpolation of the the $FindBin::Bin variable is happening correctly (this , along with value of $circos should / can be verified using perl -debug and putting a break at line 903) , the next thing to check is if the output directory (circos-p) exists on the windows machine , and is not read-only.
From an earlier question i had asked on PM , quoted strings can give undesirable results when system passes these strings to the shell. Try passing an argument list to system instead as shown in the link.
Going through the system documentation (perldoc -f system), On a technical note, you are not doing any error handling from the system command invocation to read standard error .