[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53841] Could not copy help collection to temp

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #53841] Could not copy help collection to temporary file. Cannot load sqlite database driver! with Qt 5.12
Date: Wed, 13 Feb 2019 16:39:05 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.96 Safari/537.36

Follow-up Comment #46, bug #53841 (project octave):

Aha, thank you, I think I finally understand that this is the same bug on
Windows and on GNU/Linux. If someone builds Octave from the release tarball on
ftp.gnu.org, they are running the Qt help files generated on jwe's system. So
it's essentially the same situation where you are building the docs on your
mxe-octave system with one version of Qt and reading them on a Windows system
with Qt 5.12.

It looks to me like this isn't going to be fixed at some point, this is just
the way Qt 5.12 and future versions are working, they have to upgrade the help
file from the older format. So in general Octave will always be at risk of
trying to load a help file from an older version of Qt, and we should support
that. What about the inverse, a Qt help collection built with Qt 5.12 and then
loaded on a system with Qt 5.9?

One thing I can test easily now is building in Flatpak again with Qt 5.12, but
deleting the doc/interpreter/octave_interpreter.q* files in the distribution
before running make. If I understand this right now, that should avoid this
error message because the files will have been built by the same host version
of Qt, right?

If these qch/qhc files are not safely forward and backward compatible between
Qt releases, should we be including them in the source distribution at all?


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]