Re: 32 bits time_t and Y2038 issue

On 18/03/2025 21:58, Grant Edwards wrote:

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

msys2 is totally different.  The binaries are all native Windows
binaries, and they all work within the same Windows environment as
everything else.  There are no problems using Windows-style paths
(though of course it is best to use relative paths and forward slashes
in your makefiles, #include directives, etc., for cross-platform
compatibility).  You can use the msys2 programs directly from the normal
Windows command window, or Powershell, or in batch files, or directly
from other Windows programs.

 Are the make recipes are run using a normal Unix shell (bash? ash?
bourne?) with exported environment variables as expected when running
'make' on Unix?
 

As I said in another post - no, "make" can run in any way that is convenient.  Windows command prompt, Powershell (which I seldom use), msys2 bash, started from a "tools" menu in an IDE - whatever.

The gnu make functions [e.g $(shell <whatever>)] all work as epected?
 

Yes.
To be clear, that is not a feature I have used in a particularly advanced way - I haven't used the "shell" function in a way that relies on anything that relies on a specific shell type.  But even on Windows, there's no problem with passing environment variables on to a program started in a subshell - such as an additional sub-make.

Or are there certain gnu make features you have to avoid for makefiles
to work under msys2?
 

There is nothing that I have avoided.
It is possible that there /are/ features that I would have to avoid, if I used them - I can't claim to have made use of /all/ the features of gnu make.  But I use a lot more advanced features than most make users, without trouble.