Good suggestion. I couldn't get that to work before, now I can.
Below are all the "NOT FOUND" things that occur when I run tar
from the cmd.exe prompt (tar.exe and gzip.exe are in C:\Program
Files\Bibledit-4.9.8\editor\bin).
It appears that when tar tries to fork
Thanks, I posted the patch to upstream.
http://lists.gnu.org/archive/html/libtool-patches/2017-02/msg0.html
2017-02-21 9:03 GMT+09:00 Ray Donnelly :
> Please submit your patch upstream.
>
> On Feb 19, 2017 9:47 AM, "kinichiro inoguchi"
Can you use procmon.exe to see which folders get searched then?
On Tue, Feb 21, 2017 at 2:07 AM, Matthew A. Postiff
wrote:
> Thanks Ray. Unfortunately, the path already contains the directory where tar
> and gzip reside; in fact, I have it as the first entry in the path.
>