From: Mark Sutton <aeizon.jm@gmail.com>
To: 14080@debbugs.gnu.org
Subject: bug#14080: Guile bug building from source with pkg-config
Date: Thu, 28 Mar 2013 08:11:05 +0000 [thread overview]
Message-ID: <5153FB19.1050105@gmail.com> (raw)
Hi,
I can ./configure make make install guile-2.0.7 from source, however,
when I then try in build guile-clutter or guile-ncurses from source I
get errors in both. After googling I found that I should have
./configure PKG_CONFIG=true.
When I try this, it configures okay, however, I get the following when I
make ...
./.libs/libguile-2.0.so: undefined reference to `GC_gc_no'
./.libs/libguile-2.0.so: undefined reference to `ffi_type_sint16'
./.libs/libguile-2.0.so: undefined reference to `GC_get_bytes_since_gc'
./.libs/libguile-2.0.so: undefined reference to `ffi_type_uint64'
./.libs/libguile-2.0.so: undefined reference to
`GC_register_finalizer_no_order'
./.libs/libguile-2.0.so: undefined reference to `GC_collect_a_little'
./.libs/libguile-2.0.so: undefined reference to `GC_pthread_detach'
./.libs/libguile-2.0.so: undefined reference to `GC_finalizer_notifier'
collect2: ld returned 1 exit status
make[3]: *** [guile] Error 1
make[3]: Leaving directory `/home/marks/3rd-party-src/guile-2.0.7/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/marks/3rd-party-src/guile-2.0.7/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/marks/3rd-party-src/guile-2.0.7'
make: *** [all] Error 2
marks@marks-MacBookAir:~/3rd-party-src/guile-2.0.7$
... so at the moment, I can build guile but I cannot build any extension
packages into it.
Any ideas?
--
Many thanks
Mark Sutton
next reply other threads:[~2013-03-28 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 8:11 Mark Sutton [this message]
2013-03-30 7:21 ` bug#14080: Guile bug building from source with pkg-config Mark H Weaver
[not found] ` <51574E20.5080209@gmail.com>
2013-03-30 23:10 ` Mark H Weaver
2013-03-30 23:22 ` Mark H Weaver
2013-03-31 1:04 ` David Pirotte
2013-03-31 12:16 ` Mark Sutton
2016-06-20 20:26 ` Andy Wingo
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=5153FB19.1050105@gmail.com \
--to=aeizon.jm@gmail.com \
--cc=14080@debbugs.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).