From: Ken <kstmp001@comcast.net>
To: cygwin@cygwin.com
Subject: Re: compiler-rt-5.0.1-1.tar.xz contains llvm-objdump.exe.stackdump
Date: Tue, 13 Aug 2019 01:44:00 -0000 [thread overview]
Message-ID: <4402eb98-f121-dd57-d8fd-6e9038b62cc1@comcast.net> (raw)
In-Reply-To: <ad0e0682-4156-bf36-39de-612c1b1935dc@Shaw.ca>
On 8/11/2019 10:55 PM, Brian Inglis wrote:
> On 2019-08-11 13:08, Ken wrote:
>
> Delete /llvm-objdump.exe.stackdump from the root directory, and the first line
> from the manifest /etc/setup/compiler-rt.lst.gz, so you're good again:
>
> $ zcat /etc/setup/compiler-rt.lst.gz
> llvm-objdump.exe.stackdump
> usr/
> usr/lib/
> usr/lib/clang/
> usr/lib/clang/5.0.1/
> usr/lib/clang/5.0.1/lib/
> usr/lib/clang/5.0.1/lib/windows/
> usr/lib/clang/5.0.1/lib/windows/libclang_rt.builtins-x86_64.a
> usr/share/
> usr/share/doc/
> usr/share/doc/compiler-rt/
> usr/share/doc/compiler-rt/README.txt
>
Yes, that work-around would resolve the 'Incomplete' status, but it is
not very convenient for multiple installations.
I was more hoping that the maintainer would note it on their "To Do"
list for the next package update. :D
Thanks for this specific work-around though!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-13 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 1:39 Ken
2019-08-11 19:06 ` Ken
2019-08-12 2:55 ` Brian Inglis
2019-08-13 1:44 ` Ken [this message]
2019-08-12 2:24 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-13 1:38 ` Ken
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=4402eb98-f121-dd57-d8fd-6e9038b62cc1@comcast.net \
--to=kstmp001@comcast.net \
--cc=cygwin@cygwin.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).