Hi/2. Eli Zaretskii wrote: >> Date: Sat, 14 Jan 2023 23:40:57 +0900 >> From: KO Myung-Hun <kom...@gmail.com> >> CC: bug-make@gnu.org >> >>> Please describe the use case in detail. This situation exists on >>> other platforms, not just of OS/2, and we don't do anything like that >>> for those other targets, AFAIK. Instead, the Makefile should use >>> $(EXEEXT) or somesuch to account for the issue. I don't see why OS/2 >>> should be handled differently. But maybe I'm missing something. >>> >> >> Yes, I appended $(EXEEXT) if necessary for libiconv, coreutils, and so >> on. BTW, I had a question while doing that. Because only OS/2 required >> $(EXEEXT). Windows platform such as mingw also requires it, but until I >> appended, it had not been there. In practice, make of mingw does not >> require $(EXEEXT). > > How do you mean "make of mingw does not require $(EXEEXT)"? AFAICT, > if the Makefile defines a target FOO, and there's a file FOO.exe that > is up to date wrt its dependencies, the MinGW Make will recompile > anyway, because it doesn't understand that linking FOO produces > FOO.exe. > > So I think MinGW and OS/2 are in the same wagon here.
I've tested make v3.81 for i686-pc-msys shipped with msys. -- KO Myung-Hun Using Mozilla SeaMonkey 2.7.2 Under OS/2 Warp 4 for Korean with FixPak #15 In VirtualBox v6.1.40 on Intel Core i7-3615QM 2.30GHz with 12GB RAM Korean OS/2 User Community : http://www.os2.kr/
