[Octave-bug-tracker] [bug #36076] Ghostscript executable not found with name 'gs' on Windows

[Philip Nienhuis]

Follow-up Comment #5, bug #36076 (project octave):

This bug is a bit of a intriguing one.

It must have been broken ever since at least 3.4.0, as I've had to copy
gswin32c.exe to gs.exe AFAICR.

After digging around in the code, I finally find in __print_parse_opts__.m,
subfunction __ghostscript_binary__.m (L.450) that in case of Windows, Octave
should indeed search for
{"gs.exe", "gswin32c.exe", "mgs.exe"}
...but no, that didn't work here nor on the OP's box.

However, after having stepped through the code of 3.6.1_MinGW, automagically
it now works OK on my box: it does find & use gswin32c.exe. Go figure...

BTW an alternative trick to point Octave to the Ghostscript exe is to specify
the fully qualified pathname in an environment var "GSC".

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36076>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/