From: Hans Aberg <haberg-1@telia.com>
To: 19237@debbugs.gnu.org
Subject: bug#19237: Guile-2.0.11 OS X 10.10.1 build error
Date: Mon, 1 Dec 2014 00:51:14 +0100 [thread overview]
Message-ID: <33812EC5-B247-42F7-B602-7C3E61FAFEF6@telia.com> (raw)
I get a build error [1] with guile-2.0.11 on OS X 10.10.1. It looks like an illegal int to pointer conversion cause a name to not be defined, and then the linking fails.
1. make
...
Making all in guile-readline
SNARF readline.x
/Applications/Xcode.app/Contents/Developer/usr/bin/make all-am
CC readline.lo
../../guile-2.0.11/guile-readline/readline.c:433:16: warning: implicit declaration of function 'rl_get_keymap_name' is invalid in C99
[-Wimplicit-function-declaration]
if (strncmp (rl_get_keymap_name (rl_get_keymap ()), "vi", 2))
^
../../guile-2.0.11/guile-readline/readline.c:433:16: warning: incompatible integer to pointer conversion passing 'int' to parameter of type 'const char *'
[-Wint-conversion]
if (strncmp (rl_get_keymap_name (rl_get_keymap ()), "vi", 2))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/string.h:84:26: note: passing argument to parameter here
int strncmp(const char *, const char *, size_t);
^
2 warnings generated.
CCLD libguilereadline-v-18.la
Undefined symbols for architecture x86_64:
"_rl_get_keymap_name", referenced from:
_scm_init_readline in readline.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [libguilereadline-v-18.la] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
next reply other threads:[~2014-11-30 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 23:51 Hans Aberg [this message]
2014-12-03 22:21 ` bug#19237: Guile-2.0.11 OS X 10.10.1 build error Ludovic Courtès
2014-12-03 22:32 ` Hans Aberg
2014-12-04 17:23 ` Ludovic Courtès
2014-12-04 19:28 ` Hans Aberg
2014-12-04 23:47 ` Mark H Weaver
2014-12-05 9:28 ` Hans Aberg
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=33812EC5-B247-42F7-B602-7C3E61FAFEF6@telia.com \
--to=haberg-1@telia.com \
--cc=19237@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).