Re: 32 bits time_t and Y2038 issue

On 2025-03-18, David Brown <david.brown@hesbynett.no> wrote:

Install msys2 (and the mingw-64 version of gcc, if you want a native
compiler too).  Make sure the relevant "bin" directory is on your path.
Then gnu make will work perfectly, along with all the little *nix
utilities such as touch, cp, mv, sed, etc., that makefiles sometimes use.
>
The only time I have seen problems with makefiles on Windows is when
using ancient partial make implementations, such as from Borland, along
with more advanced modern makefiles, or when someone mistakenly uses
MS's not-make "nmake" program instead of "make".

I have seen problems when using tools that are build during the compile
proess, used to generate further C code.

I would suggest using WSL instead of msys2. I have not used it for
cross-compiling, but it works fine (except for file access performance) for
my documentation process, which needs commandline pdf modification tools
plus latex.

A good makefile picks up the new files automatically and handles all the
dependencies, so often all you need is a new "make -j".

I don't do that anymore - wildcards in makefiles can lead to all kinds of
strange behaviour due to files that are left/placed somewhere but are not
really needed. I prefer to list the files I want compiled - it is not that
much work.

cu
Michael
--
Some people have no respect of age unless it is bottled.