Benjamin Kirk wrote: > Will be easy, but I bet those are not most of the ones which conflict? More > difficult will be, for example, HAVE_STDLIB_H, which comes indirectly when > configure looks for <stdlib.h>. Similarly, SIZEOF_INT etc... ?
I have vague memories of talking about this problem (with John?) at some point and deciding the solution should be simple: at the end of libmesh_config.h, each offending entry gets: #define LIBMESH_WHATEVER WHATEVER #undef WHATEVER Of course, just because the solution is simple doesn't mean it's not wrong; I may be misremembering how the C preprocessor works. --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
