Sujet : Re: 32 bits time_t and Y2038 issue
De : invalid (at) *nospam* invalid.invalid (Grant Edwards)
Groupes : comp.arch.embeddedDate : 18. Mar 2025, 21:58:33
Autres entêtes
Organisation : PANIX Public Access Internet and UNIX, NYC
Message-ID : <vrcmpp$175$1@reader1.panix.com>
References : 1 2 3 4 5 6 7
User-Agent : slrn/1.0.3 (Linux)
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