[Octave-bug-tracker] [bug #59546] Missing latex interpreter

[Markus Mützel]

Follow-up Comment #38, bug #59546 (project octave):

That seems to fail. At least, I can't see the pdf file:

>>
system('"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\libexec\octave\7.0.0\exec\x86_64-w64-mingw32\octave-svgconvert.exe"
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\sombrero.svg"
pdf 96.13
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\share\octave\7.0.0\fonts\FreeSans.otf"
1
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\output.pdf"')
ans = -1.0737e+09
>> typecast(ans, "uint64")
ans = 13965662441850273792
>> typecast(ans, "int64")
ans = -4481081631859277824


The cast of the return value to uint64 and int64 was in the hope that might be
helpful. But I'm not sure what it means.
It looks like a random number. But it is always the same.

I've ran the same command in the msys2 shell that is part of the MXE Octave
dist bundle and it *worked*.
I had to `set QT_PLUGIN_PATH=%OCTAVE_HOME%qt5\plugins` because that wasn't
done automatically. After that:

$ echo $QT_PLUGIN_PATH
D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\qt5\plugins


This variable *is* set in Octave though:

>> getenv('QT_PLUGIN_PATH')
ans =
D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\qt5\plugins


If that variable isn't set, I see the following:

Markus@Markus-PC MINGW64 ~
$
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\libexec\octave\7.0.0\exec\x86_64-w64-mingw32\octave-svgconvert.exe"
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\sombrero.svg"
pdf 96.13
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\share\octave\7.0.0\fonts\FreeSans.otf"
1
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\output.pdf"
qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.


Markus@Markus-PC MINGW64 ~
$ echo $?
127


But that is probably to be expected and unrelated to the issue here.

I tried the same at the CLI (all previous tests were done using the GUI).
On executing the command, a window with the following message popped up:
> octave-svgconvert.exe - Einsprungpunkt nicht gefunden
> Der Prozedureinsprungpunkt "_Z11qt_assert_xPKcS0_S0_i" wurde in der DLL
"D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\libexec\octave\7.0.0\exec\x86_64-w64-mingw32\octave-svgconvert.exe"
nicht gefunden.

IIUC, that means there is a missing symbol (demangled: "qt_assert_x(char
const*, char const*, char const*, int)").
The same message box repeated for "_Z5qHashRK7QStringj" (demangled:
"qHash(QString const&, unsigned int)").
Those symbols look like Qt library functions. I don't know why it isn't
looking for them in a library though. Maybe a linking error?

It is strange that it is working when called from the msys2 shell but not when
it's called from the Octave prompt.
That makes me suspicious that something might be wrong with how we run a
system command in Octave.

It's not the environment variables though afaict:

>> system('echo %QT_PLUGIN_PATH%')
D:\SVN\Octave\test\octave-2021-03-23-17-34-w64-latex\octave-2021-03-23-17-34-w64\mingw64\qt5\plugins
ans = 0


Any ideas what to do next?


    _______________________________________________________

Reply to this item at:

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

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