public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Csaba Raduly <rcsaba@gmail.com>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: clang doesn't work from cygwin-3.4.0 (Re: clang-format and clang-check return 127 and no text)
Date: Sun, 8 Jan 2023 11:02:23 +0000	[thread overview]
Message-ID: <1c6e15c2-bf73-120f-9034-1680fc6e0ea3@dronecode.org.uk> (raw)
In-Reply-To: <CAEhDDbBvTsXqxA1okBLwdZdmzfm3XXr5jmXdoBZ60Mp4u0ho8Q@mail.gmail.com>

On 08/01/2023 09:18, Csaba Raduly via Cygwin wrote:
> On Sun, 8 Jan 2023 at 09:11, ggl329 via Cygwin <cygwin@cygwin.com> wrote:
> 
> $ strace /usr/bin/clang --version
> strace.exe: error creating process C:\cygwin64\bin\clang, (error 5)

This will usually avail you naught, as clang is a Cygwin symlink, and 
strace as a pure Windows program doesn't understand those (which is what 
that error is trying to tell you)

$ strace $(realpath $(which clang))

shows the actual problem...

---------------------------
clang-8.exe - Entry Point Not Found
---------------------------
The procedure entry point _alloca could not be located in the dynamic 
link library C:\cygwin64\bin\cygLLVMSupport-8.dll.
---------------------------

... which does correspond to a change made in Cygwin 3.5.0.


  reply	other threads:[~2023-01-08 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08  8:11 ggl329
2023-01-08  9:18 ` Csaba Raduly
2023-01-08 11:02   ` Jon Turney [this message]
     [not found]     ` <CAEhDDbCcnKFxcuOVurzwA_ktnq07WUaH=HGh2cF0ymo_+1CvAQ@mail.gmail.com>
2023-01-08 15:25       ` Jon Turney
2023-01-09 13:05     ` Corinna Vinschen
2023-01-10 15:35       ` ggl329
2023-01-11  9:24         ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1c6e15c2-bf73-120f-9034-1680fc6e0ea3@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=rcsaba@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).