[Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes with Nvidia drivers

[Dan Sebald]

Follow-up Comment #92, bug #44478 (project octave):

Regarding the conflicting names question, I have nVidia driver installed.  Is
it the case then that my GL is one built by nVidia?  In some sense it doesn't
matter which is current for the following check.  We know we are linking in
both -lGL and -lOSMesa.

I do the following:


nm -D /usr/lib/x86_64-linux-gnu/libGL.so > libGL_functions.txt
nm -D /usr/lib/x86_64-linux-gnu/libOSMesa.so > libOSMesa_functions.txt


then open those two files to see if there are function names in common.  There
are, For example, I see

000000000006a1c0 T glGetIntegerv

in the libGL file, and

00000000002a8100 T glGetIntegerv

in the libOSMesa file.  (Please verify on your system if there is a similar
namespace.)

It probably would be a good idea to add some flag to Octave build that
requires unique function names.  Generally, though, I'd think that C/C++
compiler/linkers just search until they find the appropriate global name and
conclude, "it's there, next one".

I think it might be fastest to go to the Mesa/OSMesa source code and see if
what the developers have done is non-portable in some way.

In the mean time, I was searching the Internet for solutions to offscreen
rendering with OpenGL.  There are a lot of people asking how to do just that,
feeling Mesa/OSMesa isn't adequate for their system, and looking for a GL,
GLU, GLUT only solution.  There's a lot of back and forth comments, but
ultimately no good answers.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44478>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/