Conversation
The only known working implementation is for i686 MSVC. - detection was already disabled and marked at not working with amd64 MSVC, - detection was already disabled on amd64 MinGW because amd64 Windows was tested, not just amd64 MSVC, - there is no MinGW implementation in the code, - this disables detection on MinGW explicitely whatever the architecture.
275fad6 to
8edc038
Compare
8edc038 to
2265238
Compare
|
Microsoft longjmp documentation warns:
Anyway as discussed elsewhere, since 32-bit Windows is obsolete it's probably not worth trying to port this to MinGW. |
|
Actually the code is already entirely skipped on amd64 with MSVC: So actually my second commit was adding with MinGW something that was even not implemented with MSVC (on amd64). So we can just decide to just always skip the code on MinGW, which is my first commit. |
2265238 to
229f874
Compare
|
So I removed the second commit. MinGW now does like MSVC amd64: skip the tests. We already know we can skip the tests since MSVC does it in all cases with amd64. |
|
It happened that it was already skipped on MinGW amd64 too because it was just testing for |
229f874 to
b67a76b
Compare
|
To quote the remaining commit message: |
b67a76b to
0f62129
Compare
|
@slipher I need this to get the i686 MinGW build working. |
0f62129 to
0885097
Compare
|
I added a patch to silence a warning. |
I thought you gave up on using MinGW for now since the ones in Debian are too old to build it (needs GCC 16; also may depend on the right TLS flavor being configured). In view of Unvanquished/Unvanquished#3572 maybe we will never need to build an x86 MinGW version. |
Extracted from:
Replaying parts of:
Does nothing until: