From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Apps <cygwin-apps@cygwin.com>
Subject: autotools fails to find /lib/liblz.a
Date: Fri, 30 Oct 2020 12:24:57 -0600 [thread overview]
Message-ID: <e23c8f24-7374-fc6b-e0de-997504986863@SystematicSw.ab.ca> (raw)
Hi folks,
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.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with liblz and none of the candidates passed a file format test
*** using a file magic. Last file checked: /lib/liblz.a
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.
*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
Also working with upstream on the issue.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next reply other threads:[~2020-10-30 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:24 Brian Inglis [this message]
2020-10-30 19:32 ` Achim Gratz
2020-10-30 19:42 ` Ken Brown
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=e23c8f24-7374-fc6b-e0de-997504986863@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).