chuggafan

I'm currently working on it, there actually aren't as many shared warnings as I thought however...

> Hm, is this because occ does not warn the stuff GCC does or because of one of those compilers combines the warnings under a single flag while the other...

Tried this with a project for OMAKE that I'm working on to make OMAKE accept the recursive makefile calls GNU Make does so that if one calls the other we...

Yhea, I was guessing as much, I'm thinking this might be best left to deal with by actually editing the wildcard rule handling that OMake has to handle it because...

I've tested this with mingw as well: you're right that it's to do with the path specification. For now I'll work on my little threading update in Visual Studio before...

>How does this provide a command line option to debug? Why not generate debug information for GDB, too? LLDB supports the CodeView format, as well as PDB. Not sure about...

Do you happen to know which autoconfig thing or MPFR thing is doing the UINT_MAX instead of UINTMAX__MAX? I'll check it out and see what's going on if you do.

Ok so I did some digging, the only way it would "mess up" in such a way is via the AC_CHECK_TYPES([intmax_t]) failing. https://github.com/BrianGladman/mpfr/blob/master/src/mpfr-intmax.h seems to indicate that the problem lies...

Just checked, seems like there was a bug in some revision with tfits.c the test, specifically relating to uintmax_t and intmax_t, sometime ago [revision found here](https://gforge.inria.fr/scm/viewvc.php/mpfr?view=revision&revision=13457), so try the newest...

Just going back into this to mark this as a "milestone 5" issue, at least in text.