Kendall Bennett wrote:
> 
> Hi All,
> 
> We are starting to try and integrate the latest CVS sources into our
> MGL graphics library, but are having a hell of a time getting the
> code to compile properly. Specifically we are building the code using
> the Watcom C++ 11.0 compiler, and are running into problems with
> badly used token pasting and compiler warnings all over the place. Is
> anyone actually building the latest CVS sources on a regular basis
> with compilers other than GNU C on Linux? I certainly didn't expect
> to see these types of problems rampant throughout the latest CVS
> sources.
> 
> The problem with token pasting is simple to fix. The code is
> currently constructed like so:
> 
> #define TAB(x)   blah_blah_##x##_table
> 
> and used like so:
> 
>  TAB(4ub);
> 
> The problem with this is that the '4ub' value passed to the macro is
> interpeted by many compilers as the unsigned value 4 followed by the
> character b. The solution to this problem (and what we do in our code
> where we do this type of thing) is to always use an underscore in
> front of the names passed to macros that use token pasting:
> 
> #define TAB(x)   blah_blah##x##_table
> 
>  TAB(_4ub);
> 
> We are changing our sources to fix this, but I don't have CVS set up
> on the machine that we are doing this with at the moment. Hence it
> would be appreciated if this change could be made to the CVS sources.

Sounds like a reasonable change.  I'm kind of busy with other things
though.  Anyone else?


> As for the compiler warnings, when I get some time I will look into
> the problems and figure out how to work around them to get a clean
> build.

I had been building regularly on IRIX and that often caught problems
that gcc didn't.  However, I don't have a compiler on my O2 at this
time.

If anyone else has access to non-GNU compilers, I encourage you to
compile Mesa and see if there's problems.

-Brian


_______________________________________________
Mesa-dev maillist  -  [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev

Reply via email to