Hi/2. Paul Smith wrote: > On Fri, 2023-01-13 at 22:27 +0900, KO Myung-Hun wrote: >> This pattern is usually used on UNIX. However, on OS/2, gcc creates >> foo.exe not foo when an extension is not present, and Make check foo >> only. Therefore Make tries to build foo whenever called. > > I don't think I like this change. I understand its usefulness but in > general make never tries to manipulate the target names like this. If > users want to create a file named "foo.exe" they should use that as the > target name. > > I get that it's super-annoying that when you ask GCC to build a file > named "foo" via "-o $@" it will actually create a file named "foo.exe" > instead, but I think that's something that makefile authors will have > to deal with, rather than make. >
I agree. But as you said, it's true that it's far less burden to porters. > What do you do in situations where there are targets for BOTH "foo" and > "foo.exe" in the makefile? Then when you want to build "foo" it may > decide that it's up to date, because it sees the "foo.exe" file > instead. In this case, Make should not find "foo.exe" for "foo" target. I willing to modify my patch for this. Thanks! -- 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/
