So far I've been able to cross-compile Gnuastro for the following platforms without issues (apart from i686-linux-musl, but that was a known issue with the toolchain I'm using):

• i686-linux-gnu
• x86_64-linux-gnu
• aarch64-linux-gnu
• arm-linux-gnueabihf
• powerpc64le-linux-gnu
• i686-linux-musl
• x86_64-linux-musl
• aarch64-linux-musl
• arm-linux-musleabihf
• x86_64-apple-darwin14
• x86_64-unknown-freebsd11.1

If you're curious, this is the tool I'm using to cross-compile: https://binarybuilder.org/

> Generally, are the Gnuastro dependencies install-able on Windows (on MinGW?). If they are, it is worth considering, by a professional Windows user.

I'm using the following dependencies (am I missing something?):

• CFITSIO,
• GSL,
• JpegTurbo,
• Libtiff,
• LibGit2,
• WCSLIB.

All of them can be compiled for Windows with MinGW.  CFITSIO and WCSLIB require some special treatment because of names clashing.  `wcsset` is not the only function clashing: CFITSIO uses a macro called `TBYTE`, which is also a macro in MinGW.  BTW, also Gnuastro uses `TBYTE`.

I think I'll give up building Gnuastro for Windows for the time being.  We can keep this issue open in case you want to reconsider support for Windows.  I'd be happy to test compilation with MinGW, if you need to

On a related note, are you aware of Gnuastro being compiled for Windows?  Seeing a fair share of issues -- not all of them directly coming from Gnuastro -- I'm starting to doubt that anyone ever tried it :-)

Ok, I promise this is a real bug in Gnuastro :-)

MinGW doesn't have tm_zone field in the tm struct, this is used in fits.c.  Note that autoconf has a macro to check this: `HAVE_STRUCT_TM_TM_ZONE`, see https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Particular-Structures.html