From: Eli Zaretskii <eliz@gnu.org>
To: guile-user@gnu.org
Subject: guile-2.0.pc misses a few dependency libraries
Date: Sat, 28 Jan 2012 13:20:21 +0200 [thread overview]
Message-ID: <83mx98xedm.fsf@gnu.org> (raw)
When statically linking programs against libguile-2.0.a, I get
unresolved externals. This is on MS-Windows, but I don't think this
is related to the problem.
I finally traced that to the contents of guile-2.0.pc file:
Libs: -L${libdir} -lguile-2.0 -Ld:/usr/lib -lgc
Libs.private: d:/usr/lib/libgmp.dll.a -Ld:/usr/lib d:/usr/lib/libltdl.dll.a -Ld:/usr/lib -lffi -lregex -lcrypt -lws2_32 -lm
However, libguile-2.0.la shows more dependency libraries:
dependency_libs=' -lgc -lffi -lunistring -liconv -lregex -lintl -liconv -lgmp -ltdl -lregex -lintl -lwsock32 -lole32 -luuid -lmsvcp60 -lcrypt -lws2_32'
As you see, quite a few libraries are missing from guile-2.0.pc, and
also a several libraries need to appear more than once in the link
command line.
Why doesn't the Guile build process put all of the libraries in the
.pc file?
I could easily work around this by editing guile-2.0.pc manually, but
isn't this supposed to happen automatically?
Any help would be appreciated.
next reply other threads:[~2012-01-28 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 11:20 Eli Zaretskii [this message]
2012-01-29 23:19 ` guile-2.0.pc misses a few dependency libraries Ludovic Courtès
2012-01-30 17:02 ` Mark H Weaver
2012-01-30 17:10 ` Ludovic Courtès
2012-01-31 16:57 ` Eli Zaretskii
2012-01-31 17:56 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mx98xedm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=guile-user@gnu.org \
/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).