[Octave-bug-tracker] [bug #55735] QGLWidget not detected, so Qt graphics toolkit is not compiled

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?55735>

                 Summary: QGLWidget not detected, so Qt graphics toolkit is
not compiled
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Mon 18 Feb 2019 03:39:57 AM UTC
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: jwoithe
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.0.91
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Affected distributions: Slackware64 14.2 with all updates applied,
Slackware64-current from 2019/Feb/13.

Octave 5.0.91-7b9a5ab8350f was configured using


mkdir build && cd build
../configure --with-blas=openblas --libdir=/usr/local/lib64 --disable-docs


The configure script failed to detect the presence of QGLWidget on the system,
concluded that OpenGL didn't work with Qt, and disabled OpenGL graphics with
Qt GUI.  Although it wasn't obvious from the messages, this meant the Qt
graphics toolkit was not compiled.  Attempting to use GUI elements in Octave
code resulted in complaints from the gnuplot module that uicontrol was an
unknown object.

The reason for the failure is that the test program from "configure" gave "no
such file or directory" for QGLWidget's include line.  Looking in config.log
at the compiler flags, the include paths given to the compiler did not include
those of the QtOpenGL module.  This is because in "configure" only QT_CPPFLAGS
is referenced, and this is constructed using only QT_MODULES: QT_OPENGL_MODULE
is not included.

In "configure" from Octave 4.4.x, QT_OPENGL_MODULE did not exist and QtOpenGL
was included in QT_MODULES.  That is, Octave 4.4.x on the same system did not
have this issue.

By editing "configure" and putting QtOpenGL in QT_MODULES I am able to obtain
a version of Octave 5.0.91 which includes the qt toolkit.

The systems have Qt version 4.8.7 installed.  However, the Qt5 case in
"configure" also similarly separates Qt5OpenGL from QT_MODULES, so the issue
may occur for Qt5 as well.

Unfortunately I am not familiar enough with autoconf to determine how this is
occurring based on configure.ac.  I note that the "configure" script from
Octave 4.4.1 does not define QT_OPENGL_MODULE, with QtOpenGL included in
QT_MODULES.  Could this be due to an autoconf issue rather than Octave, given
that 4.4.1's "configure" is supplied in the source tarball while 5.0.91's is
locally generated by the bootstrap process?  Both Slackware64-14.2 and
Slackware64-current-20190213 systems have autoconf 2.69.

I have attached the "configure" script originally produced when bootstrapping
5.0.91 for reference.

I'm more than happy to assist in debugging this further.




    _______________________________________________________

Reply to this item at:

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

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