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
After a perl script builds inline CPP, a .lock file is left over in the PERL_INLINE_DIRECTORY under the username of the running user. This prevents subsequent runs by other users who share the same PERL_INLINE_DIRECTORY and cannot delete the lock file left over. We are seeing this on Red hat linux with perl version 5.20.2, inline:CPP version 0.71, Inline::C 0.74. The Inline CPP folks are directing me to Inline and/or Inline::C. See daoswald/Inline-CPP#29 . The issue goes away after removing file locking code in Inline::CPP - CPP.pm lines 681,682 even though no lock file with a .lock signature is being created at that point (from David's investigation/understanding).
The text was updated successfully, but these errors were encountered:
@anthonybakermpls, not to say this is your problem to fix, but if you do a search in Inline's lib/Inline.pm, you'll find calls to flock(). Can you experiment with those?
After a perl script builds inline CPP, a .lock file is left over in the PERL_INLINE_DIRECTORY under the username of the running user. This prevents subsequent runs by other users who share the same PERL_INLINE_DIRECTORY and cannot delete the lock file left over. We are seeing this on Red hat linux with perl version 5.20.2, inline:CPP version 0.71, Inline::C 0.74. The Inline CPP folks are directing me to Inline and/or Inline::C. See daoswald/Inline-CPP#29 . The issue goes away after removing file locking code in Inline::CPP - CPP.pm lines 681,682 even though no lock file with a .lock signature is being created at that point (from David's investigation/understanding).
The text was updated successfully, but these errors were encountered: