On Mon Sep 24 15:58:21 2012, LAWALSH wrote:
Show quoted text> Normal build failed, so jumped into build dir to run things manually.
>
> Got -- the perl MakefilePL and make seem to go 'ok':
> Ishtar:cache/../build/OpenGL-0.66-Td9wnB> perl Makefile.PL
>
> In order to test your GPU's capabilities, run this make under an X11
> shell
...
Show quoted text> Using Mipmap
> make: *** [test_dynamic] Segmentation fault (core dumped)
>
> --------
> (gdb) where)
> #0 0x00007f9c99f2ec06 in __memcpy_ssse3_back () from /lib64/libc.so.6
> #1 0x000000301482dd05 in ?? () from /usr/lib64/libGL.so.1
> #2 0x00007f9c99b7f0a7 in XS_OpenGL_glGenProgramsARB_p (
> my_perl=<optimized out>, cv=<optimized out>) at
> pogl_gl_Mult_Prog.xs:1843
> #3 0x00000000004a6ee2 in Perl_pp_entersub ()
> #4 0x000000000049f6a6 in Perl_runops_standard ()
> #5 0x000000000043caf4 in perl_run ()
> #6 0x000000000041ec5b in main ()
>
>
> ??? Note -- I am trying to build this via a remote 'X' session (using
> cygwin X as remote display -- not expecting 'speed', though NW
> connection is 1Gb.
>
> It doesn't seem to be using FREEGLUT but appears to be trying to use
> opengL directly? (i.e. though freeglut supported remote??)
Looking at this one again, didn't see this the
first time. By default, a cygwin build of the perl
OpenGL module will use the WGL/win32 native
OpenGL library. That is why it was being called
even though the session was an X/network one.
If you want the network OpenGL support,
you would (presumably) need to link in the
FreeGLUT + Mesa libraries in place of the
win32 ones.
Cygwin support for accelerated X/GLX has
improved and it may now be possible to
choose which to link to without the hoops
of sticking in the explicit win32 libs.
I'm looking at this issue along with dynamic
configuration for the next OpenGL release.
--Chris