[Octave-bug-tracker] [bug #57143] print ('-tight', 'q.eps') produces no file

[Kai Torben Ohlhus]

Follow-up Comment #15, bug #57143 (project octave):

Maybe I came a step closer to the root cause.  In short: epstool cannot invoke
ghostscript correctly due to a hardcoded bad assumption.

Details:

I tried the fix of Rik comment #13.  Indeed this can be changed, as it has no
effect on the output of the first step calling ghostscript (gs.exe).  But it
was not the solution.

Next I committed the cleanup "& del ..." and removed the "--quiet" option from
the "epstool.exe" call.  This revealed two things:

1. The temporary file by the first step in the pipeline of gs.exe is created.
2. The further processing by epstool.exe is broken.

The same happens from Octave, but I invoked the command directly from the temp
directory to show the details:


>> system ("epstool.exe --copy --bbox oct-GAt3ba.eps blub.eps")
"gswin32c.exe"  -dNOPAUSE -dBATCH -sDEVICE=bbox   -c "<</PageSize [9400 9400]
/PageOffset [30
00 3000]>> setpagedevice" -f
"c:\users\siko1056\appdata\local\temp\gsviewa06976"
Ghostscript failed to obtain bounding box
Failed
ans = 1


Especially, I was curious about "gswin32c.exe".  Octave's Ghostscript is
called "gs.exe".


>> system ("where gs")
C:\Octave\Octave-6.0.1\mingw64\bin\gs.exe
ans = 0

>> system ("where gswin32c")
INFO: Could not find files for the given pattern(s).
ans = 1

>> system ("where gswin32c.exe")
INFO: Could not find files for the given pattern(s).
ans = 1

>> system ("gswin32c.exe")
'gswin32c.exe' is not recognized as an internal or external command,
operable program or batch file.


In epstool-3.08 this decision is hardcoded (src/epstool.c):


#ifdef _WIN32
TCHAR gsexe[MAXSTR] = TEXT("gswin32c.exe");
#define COLOUR_DEVICE TEXT("bmp16m")
#define GREY_DEVICE TEXT("bmpgray")
#define MONO_DEVICE TEXT("bmpmono")
#endif


Maybe MXE needs to patch this file?

Further note:  There is an epstool-3.09, but the tar.gz file seems to be
broken.  I'll contact the maintainer to ask for advice.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57143>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/