The check in octave isn't obsolete, but the error message isn't entirely accurate anymore. In your case it is failing because of libglvnd, not because of an old osmesa.
If this is working for you you should mark this thread as [SOLVED].
]]>In /usr/include/GL/gl.h:
GL_DEPTH_BITS is defined as 0x0D56
GL_STENCIL_BITS is defined as 0x0D57
But according to /usr/include/GL/osmesa.h (which includes GL/gl.h), OSMESA is at version 11.2.0, so probably isn't susceptable to the bug this check is meant to protect against.
I would second the Octave bug conclusion. You could try adding an extra check around the offending octave code to see if OSMESA_MAJOR_VERSION < 10 before it checks the GL BITS, then recompile octave and see if you still have problems.
]]>--enable-gallium-osmesa \
even mesa-git is at libOSMesa.so.8.0.0 , maybe classic OSMesa (which is what's build when using --enable-osmesa ) has a different version scheme ?
Either way, this sounds like an upstream bug that needs to be reported to Octave developers.
specifically the error I get in octave is
error: __osmesa_print__: Depth and stencil doesn't match, are you sure you are using OSMesa >= 9.0?
I checked which library version is installed and it appears the 8.0 is there
> ls /usr/lib/libOSMesa* -1
/usr/lib/libOSMesa.so
/usr/lib/libOSMesa.so.8
/usr/lib/libOSMesa.so.8.0.0
and
> pacman -Qo /usr/lib/libOSMesa.so
/usr/lib/libOSMesa.so is owned by mesa 17.2.5-1
According to
https://www.mesa3d.org/osmesa.html
the option --enable-osmesa is required while configuring the pkgs which I see it is not done in
https://git.archlinux.org/svntogit/pack … kages/mesa
could someone help me in installing a modified pacman pkg with that option and use it to replace the currently installed version?
]]>