Personal tools
You are here: Home → Forum → Extension of the platform → Mandriva rpm package - some problems
 

Mandriva rpm package - some problems

Up to Extension of the platform

Mandriva rpm package - some problems

Posted by Paulo Cesar Pereira de Andrade at March 26. 2010

  Hi,

  I am working on a Mandriva cooker (2010.1 or newer) rpm package of salome, and opencascade.

Currently most of it is built, a screenshot:

http://img683.imageshack.us/img683/3971/salomemandrivacooker.png

[not attaching 80Kb screenshot for first post...]

But I am having some issues with OpenCascade OpenGl driver.

 

  For example, in one computer, when running:

% MESA_DEBUG=FP LIBGL_DEBUG=verbose runSalome

after several salome debug output, when selecting the geometry module,

I see from Xorg/Mesa:

 

libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)

libGL: OpenDriver: trying /usr/lib64/dri/r300_dri.so

Using x11AppColormap

libGL: Can't open configuration file /etc/drirc: Arquivo ou diretório não encontrado.

Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable

Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)

Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)

Mesa: 1 similar GL_INVALID_ENUM errors

Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)

Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)

Mesa: 1 similar GL_INVALID_ENUM errors

Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)

Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)

Mesa: 1 similar GL_INVALID_ENUM errors

Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)

Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)

Mesa: 1 similar GL_INVALID_ENUM errors

Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)

Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)

Mesa: 1 similar GL_INVALID_ENUM errors

Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)

Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)

 

  If I understand it correct, 0xb72 should be GL_DEPTH_WRITEMASK, so, it may be

a problem in mesa.

 

  And, if I tell it to show anything, it will keep showing messages about SIGFPE.

 

  In another computer, with an intel video card, I get even worse results, as it fails

in some initialization step.

 

  But, if I reconfigure the X Server to use fbdev or vesa video driver (to force software

rendering), and restart the X Server, it appears to work correctly.

 

  I understand it should be a problem to be reported to Xorg/Mesa, but any hints on how

the precompiled salome/opencascade handles it is welcome, as it should not be much

easy to "convince" some upstream Xorg/Mesa developer to install bleeding edge

Mandriva and packages to debug, so I am trying to get some hints on how to debug it...

 

Thanks,

Paulo

 

 

Powered by Ploneboard
Document Actions