From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: autotools fails to find /lib/liblz.a
Date: Fri, 30 Oct 2020 15:42:31 -0400 [thread overview]
Message-ID: <5e8e53db-482f-eac6-c193-d4bd62e91676@cornell.edu> (raw)
In-Reply-To: <87pn4zy0gf.fsf@Rainer.invalid>
On 10/30/2020 3:32 PM, Achim Gratz wrote:
> Brian Inglis writes:
>> Hoping this is a symptom of a well known issue with a well known solution, or I
>> can get the build to work without it:
>>
>> CCLD libwget.la
>>
>> *** Warning: linker path does not have real file for library -llz.
>
> That sounds like a bug in configure for whatever you are trying to build
> (you didn't say). First off, it shouldn't even look for a static
> library and none of that name exists in Cygwin. Also, if you need to
> figure out what goes wrong you'd better advise make to output the full
> command lines and not abbreviate (you will probably need to add V=1 or
> something like that to the arguments).
Whatever Brian is building appears to be looking for the lzlib library
(https://www.nongnu.org/lzip/lzlib.html), which in some distros, such as Debian,
is provided by a liblz-dev package. As you said, it's not in Cygwin.
I would have expected the configure script to detect that Cygwin doesn't have it.
Ken
next prev parent reply other threads:[~2020-10-30 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:24 Brian Inglis
2020-10-30 19:32 ` Achim Gratz
2020-10-30 19:42 ` Ken Brown [this message]
2020-10-30 20:05 ` Brian Inglis
2020-10-30 19:57 ` Brian Inglis
2020-10-30 21:03 ` Achim Gratz
2020-10-30 21:51 ` Brian Inglis
2020-10-31 7:43 ` ASSI
2020-10-31 19:27 ` Brian Inglis
2020-10-31 21:52 ` Achim Gratz
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=5e8e53db-482f-eac6-c193-d4bd62e91676@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).