Expanding on Keith's observation: You could conveniently confirm his hypothesis by inserting these lines at the top of sqlite3.c:<code> #undef MIN #undef MAX </code>. If that eliminates the warning, then a careful look at the expansion without those insertions is warranted. C compilers usually have an option, (typically -E), to produce preprocessed output, where you can see the macro expansions. Then you can at least see the problematic expansion. It will be more of a challenge to discover where the #define is located, but the -E output will also show you what files were made part of the compilation unit. (There will be quite a few, but only a subset of them will #define MIN and MAX.)