Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: David Brown <david.brown@hesbynett.no>
Newsgroups: comp.arch.embedded
Subject: Re: 32 bits time_t and Y2038 issue
Date: Wed, 19 Mar 2025 08:24:32 +0100
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <vrdrfg$bv66$1@dont-email.me>
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> <vrcmpp$175$1@reader1.panix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 19 Mar 2025 08:24:35 +0100 (CET)
Injection-Info: dont-email.me; posting-host="1d916a32c2f1effdd5bad6b690159690";
	logging-data="392390"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+VOy7Ps7Y4RyMffWpw0dAUc/cxkKjZ9J4="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:gGHm9H2qzyLXgTG7IU/x3c/m2EU=
In-Reply-To: <vrcmpp$175$1@reader1.panix.com>
Content-Language: en-GB
Bytes: 3126

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.