Eric Bavier writes: > The problem appears if you do not have 'perl' available in $PATH. GNU > parallel calls it recursively for a few tasks:
This is correct. I have verified it. When I have perl in my PATH, GNU parallel works fine. > There is some path patching that goes on in the package recipe, but it > must have gone out of sync in latest versions. The 'post-install-test' > phase wouldn't catch this particular error without '(setenv "PATH" "")'. > > I wouldn't feel quite comfortable doing a "blind" update of the regex, > since some mentions of "perl" I think are meant to be executed by > remote hosts and so shouldn't be patched to absolute store references. Why does parallel need to execute perl on remote hosts? > It might be useful to get Ole's opinion on this. Yes, could you please do this? Thanks!
