[MacPorts] #13517: gtkglext 1.2 configure: error -- build failure OSX 10.5

MacPorts noreply at macports.org
Mon Mar 2 18:25:57 PST 2009


#13517: gtkglext 1.2 configure: error -- build failure OSX 10.5
-----------------------------------------+----------------------------------
  Reporter:  michaelt@…                  |       Owner:  rowue@…               
      Type:  defect                      |      Status:  reopened              
  Priority:  Normal                      |   Milestone:  Port Bugs             
 Component:  ports                       |     Version:  1.7.0                 
Resolution:                              |    Keywords:  gtkglext gwyddion mesa
      Port:  gtkglext                    |  
-----------------------------------------+----------------------------------

Comment(by rowue@…):

 Trying ''glxinfo'' with xorg-server I get:


 {{{
 bratapfel:~ rowue$ glxinfo
 name of display: :0.0
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 X Error of failed request:  GLXBadContext
   Major opcode of failed request:  0 ()
   Serial number of failed request:  16
   Current serial number in output stream:  16
 bratapfel:~ rowue$
 }}}

 gwyddion crashes when using gl


 {{{
 bratapfel:~ rowue$ gwyddion
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 Xlib:  extension "RANDR" missing on display ":0.0".
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 Xlib:  extension "Generic Event Extension" missing on display ":0.0".
 The program 'gwyddion' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'GLXBadContext'.
   (Details: serial 9490 error_code 147 request_code 0 minor_code 3)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 bratapfel:~ rowue$
 }}}

 ''X11SDK'' is still present - should I remove it?

 reg's

    rowue

-- 
Ticket URL: <http://trac.macports.org/ticket/13517#comment:57>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list