Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.localhost!not-for-mail
From: Grant Edwards <invalid@invalid.invalid>
Newsgroups: comp.arch.embedded
Subject: Re: 32 bits time_t and Y2038 issue
Date: Tue, 18 Mar 2025 20:58:33 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vrcmpp$175$1@reader1.panix.com>
References: <vqpkf9$1sbsa$1@dont-email.me> <vqpoi3$226ih$1@dont-email.me>
 <slrnvtbaot.sal.news-1513678000@a-tuin.ms.intern>
 <vrbado$2133a$1@dont-email.me> <vrbi79$2a30t$1@dont-email.me>
 <slrnvtjeq9.566.news-1513678000@a-tuin.ms.intern>
 <vrcidh$35fbp$2@dont-email.me>
Injection-Date: Tue, 18 Mar 2025 20:58:33 -0000 (UTC)
Injection-Info: reader1.panix.com; posting-host="localhost:::1";
	logging-data="1253"; mail-complaints-to="abuse@panix.com"
User-Agent: slrn/1.0.3 (Linux)
Bytes: 1841
Lines: 25

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?

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

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

--
Grant