From: <ha...@ba...> - 2004-01-07 15:41:59
|
> Looks like a problem with the new def_max_anisotropy option. It's the > first floating-point option. I don't understand why this is happening, > though. It works just fine in the radeon driver and the definitions of > __driConfigOptions are identical in both drivers (see r200_screen.c). > > Also, you should see the same problem with any OpenGL app. If this is > application-specific then it's really mysterious. > > Can you send the output of "xdriinfo options r200"? I have just experienced the same problem. The problem is that character which strtod recognise as decimal point depends on current locale. And in xmlconfig.c there is this part of code: case DRI_FLOAT: v->_float =3D strtod (string, (char **)&tail); break; And if the locale is set (which could be done by application or library like Xt), the parser will fail. Because of that I think that this code shouldn't depend on strtod(). The GNU extensions that allow to select locale in strtod call are non-standard. I think that best approach would be to have internal strtod do the conversi= on. Here is small trivial patch that do it. Sincerely Pavel Pal=E1t P.S.: This is my first post and patch here, so sorry for any inconvenience ;-) -- Pavel "harry_x" Pal=E1t ha...@ba... irc: #mistral.cz on IRCnet The only way of finding the limits to the possible is by going beyond t= hem to the impossible Arthur C. Clark |