From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Vijaya Subramanian <vijaya612@yahoo.com>
Subject: Re: cmake install; required cyglz4-1.dll not installed in /usr/bin or anywhere else
Date: Tue, 05 Dec 2017 12:29:00 -0000 [thread overview]
Message-ID: <85f757cd-dfeb-8857-f5cf-85047b939e40@dronecode.org.uk> (raw)
In-Reply-To: <932804728.1590238.1512434228876@mail.yahoo.com>
Please read http://cygwin.com/problems.html#personal-email, particularly
the section starting "Shouldn't I just send email to straight to a
Cygwin developer or package maintainer?"
On 05/12/2017 00:37, Vijaya Subramanian wrote:
> When I try to run cmake, I get the following error message:
> C:/cygwin64/bin/cmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
>
> I found online that the solution was run "cygcheck cmake" and see if there are missing dll files. It does say cyglz4_1.dll is missing.If there is any other reason why running cmake gives the above error message, I'ld be happy to implement the solution/fix.
> Thanks in advanceVijaya
The dependency on liblz4 exists, so setup should have installed this
package.
It might be worthwhile looking at /var/log/setup to see if there are any
indications of why this didn't happen.
> On Sunday, December 3, 2017, 10:15:59 AM MST, Jon Turney wrote:
>
> On 03/12/2017 17:08, Achim Gratz wrote:
>> cyg Simple writes:
>>> One might ask that if setup stated it updated the package why it doesn't
>>> exist and why reinstalling it would be needed?
>
> Perhaps setup has bugs? :)
>
>> The real question is:Â Why does cmake not require liblz4_1 if it depends
>> on it? That is the most likely reason why the package wasn't installed
>> to begin with and hence an update wouldn't do anything about it.
>
> The dependency is cmake -> libarchive13 -> liblz4_1
--
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:[~2017-12-05 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1025849766.461853.1512257412645.ref@mail.yahoo.com>
2017-12-02 23:30 ` Vijaya Subramanian via cygwin
2017-12-03 9:46 ` Marco Atzeri
2017-12-03 16:55 ` cyg Simple
2017-12-03 17:09 ` Achim Gratz
2017-12-03 17:15 ` Jon Turney
[not found] ` <932804728.1590238.1512434228876@mail.yahoo.com>
2017-12-05 12:29 ` Jon Turney [this message]
[not found] <636587926.1255909.1513705410399.ref@mail.yahoo.com>
2017-12-19 18:18 ` Vijaya Subramanian via cygwin
2017-12-19 18:45 ` Brian Inglis
2017-12-20 16:02 ` Jon Turney
2017-12-20 20:38 ` Vijaya Subramanian via cygwin
2017-12-20 20:49 ` Ken Brown
2017-12-20 21:44 ` Vijaya Subramanian via cygwin
2017-12-20 23:33 ` Ken Brown
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=85f757cd-dfeb-8857-f5cf-85047b939e40@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=vijaya612@yahoo.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).