On 2002-03-11 07:34 -0800, Ricardo Rugerio wrote: > > but that is so weird! > > I had compiled it in my linux box, without > changues, and I am using gcc version 2.95.2 > > the fix that you say is like this: > > changue this line : > > extern XUnionRegion(.... > > into this line > > extern float XUnionRegion(.... > > for example???
Rick, This is not an Xmame problem, this is a Sun problem. The X headers (Xutil.h and friends) included with certain versions of Solaris are written in a dialect of C that modern compilers frown upon. In this case, they include function prototypes that don't specify what the function returns. Since C exists, if you don't specify what a function returns, the compiler assumes it's "int". This practice has been deprecated for many years. The new standard (1999) has made it illegal. The compiler you're using enforces the 1999 standard and rejects those headers. You can : - edit the system headers to add "int" in front of all typeless function prototypes. Your sysadmin might not appreciate. - look on Sun's site for the appropriate patch and ask your sysadmin to apply it. - try another compiler, like GCC. - look in the doc of your compiler for an option to turn these errors into warnings (the equivalent of GCC's -fpermissive). -- Andr� Majorel <URL:http://www.teaser.fr/~amajorel/> std::disclaimer ("Not speaking for my employer"); _______________________________________________ Xmame mailing list [EMAIL PROTECTED] http://toybox.twisted.org.uk/mailman/listinfo/xmame
