Re: clang doesn't work from cygwin-3.4.0 (Re: clang-format and clang-check return 127 and no text)

[Csaba Raduly <rcsaba@gmail.com>]

On Sun, 8 Jan 2023 at 09:11, ggl329 via Cygwin <cygwin@cygwin.com> wrote:
>
> In my environment, clang doesn't work as reported in
> https://cygwin.com/pipermail/cygwin/2022-December/252719.html .
>
> I found that it doesn't work with cygwin-3.4.0-1,
> but works with cygwin-3.3.6-1.
> cygwin-3.5.0-0.69.g8a003605c1df doesn't help.
> Changes in cygwin-3.4.0-1 bring this issue?
> or clang needs to be rebuilt?
>
> clang                                   8.0.1-1
[snip]

This was working before I upgraded Cygwin:

$ clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin

$ clang-format.exe --version
clang-format version 8.0.1 (tags/RELEASE_801/final)

$ uname -a
CYGWIN_NT-10.0-19045 AMDAHL 3.3.5-341.x86_64 2022-05-13 12:27 UTC x86_64 Cygwin

But it doesn't work anymore with

$ uname -a
CYGWIN_NT-10.0-19045 AMDAHL 3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64 Cygwin

(same symptom as https://cygwin.com/pipermail/cygwin/2022-December/252719.html)

Additionally,

$ strace /usr/bin/clang --version
strace.exe: error creating process C:\cygwin64\bin\clang, (error 5)

$ gdb -q /usr/bin/clang -ex run
Reading symbols from /usr/bin/clang...
(No debugging symbols found in /usr/bin/clang)
Starting program: /usr/bin/clang
[New Thread 804.0x2d50]
[New Thread 804.0xe6c]
[New Thread 804.0x200c]
[Thread 804.0xe6c exited with code 3221225785]
[Thread 804.0x10b8 exited with code 3221225785]
[Thread 804.0x2d50 exited with code 3221225785]
During startup program exited with code 0xc0000139.

0xC0000139 is "Entry point not found"

Csaba
-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)