config-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rethinking configuration tuples


From: John Ericson
Subject: Re: Rethinking configuration tuples
Date: Tue, 19 Sep 2023 20:02:56 -0400
User-agent: Mozilla Thunderbird

Thanks Dmitry. This is an acceptable outcome to me. It is a nice middle ground between Po Lu's and my first choice options.

John

On 9/19/23 19:58, Dmitry V. Levin wrote:
On Thu, Sep 14, 2023 at 12:55:06AM -0400, John Ericson wrote:
OK here we go:

  1. https://github.com/ericson2314/gnu-config/commit/windows-mingnu.patch
  2. https://github.com/ericson2314/gnu-config/commit/windows-mingw.patch
  3. https://github.com/ericson2314/gnu-config/commit/no-windows-gnu.patch

I tried to honestly argue for each of them the best I could in the
commit message. I know I prefer (1); I am guessing Jacob prefers (2),
and Po Lu prefers (3).

Have fun, Dmitry :).
I'm inclined to remove windows-gnu from config.sub instead of renaming or
canonicalizing it because, firstly, there is no GNU libc on windows, and,
secondly, windows-gnu as used by LLVM means MinGW, but for that we already
have mingw*, and we should avoid adding new canonical names for the same
thing.  We could add canonicalization of windows-mingw* into mingw*, but
if nobody uses the former, why bother?

At the same time, I'm inclined to leave windows-msvc as is because,
unlike windows-gnu, it does exist, and the only one who objected against
windows-msvc and suggested to canonicalize windows-msvc into winnt was
Po Lu, but the arguments provided against windows-msvc were not convincing.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]