From: dsmich@roadrunner.com
To: "'John Cowan'" <cowan@ccil.org>
Cc: "'39118@debbugs.gnu.org'" <39118@debbugs.gnu.org>,
"'Ludovic Courtès'" <ludo@gnu.org>,
"'guile-devel@gnu.org'" <guile-devel@gnu.org>
Subject: RE: bug#39118: Segfault while building on 64-bit Cygwin
Date: Fri, 24 Jan 2020 15:26:42 +0000 [thread overview]
Message-ID: <99218b8d8f572c8748963924e82d265652487a09@webmail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Pretty sure that the missing readline symbol is because the macos
readline is being used/found instead of GNU readline.
-Dale
-----------------------------------------From: "John Cowan"
To: "Ludovic Courtès"
Cc: 39118@debbugs.gnu.org, guile-devel@gnu.org
Sent: Friday January 24 2020 9:36:59AM
Subject: bug#39118: Segfault while building on 64-bit Cygwin
Both Cygwin and MacOS crash in pretty much the same way. By disabling
the JIT, I was able to get the Cygwin build to run to completion. On
MacOS with --disable-jit, however, I am now getting an entirely new
failure:
CC readline.lo
readline.c:432:7: warning: implicitly declaring library function
'strncmp' with type 'int (const char *, const char *,
unsigned long)' [-Wimplicit-function-declaration]
if (strncmp (rl_get_keymap_name (rl_get_keymap ()), "vi", 2))
^
readline.c:432:7: note: include the header or explicitly provide a
declaration for 'strncmp'
readline.c:432: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))
^
readline.c:432: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))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 warnings generated.
CCLD guile-readline.la [1]
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)
On Thu, Jan 23, 2020 at 3:35 PM Ludovic Courtès wrote:
Hi,
John Cowan skribis:
> Thanks. Unfortunately, the standard recipe for making core dumps on
Mac
This bug report is about Cygwin, not macOS, right? :-)
Ludo’.
Links:
------
[1] http://guile-readline.la
[2] mailto:ludo@gnu.org
[3] mailto:cowan@ccil.org
[-- Attachment #2: Type: text/html, Size: 2891 bytes --]
next reply other threads:[~2020-01-24 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 15:26 dsmich [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-13 8:39 GNU Guile 2.9.9 Released [beta] Andy Wingo
2020-01-13 17:26 ` John Cowan
2020-01-20 16:35 ` bug#39118: Segfault while building on 64-bit Cygwin Ludovic Courtès
2020-01-20 16:38 ` John Cowan
2020-01-20 17:22 ` bug#39118: " Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-01-21 9:01 ` Ludovic Courtès
2020-01-21 18:40 ` bug#39118: " szgyg
2020-01-21 21:53 ` John Cowan
2020-01-21 21:37 ` John Cowan
2020-01-23 20:35 ` Ludovic Courtès
2020-01-24 14:36 ` John Cowan
2020-01-25 13:51 ` Ludovic Courtès
2020-01-25 15:54 ` John Cowan
2020-01-31 14:23 ` bug#39118: " John Cowan
2020-02-03 22:11 ` szgyg
2020-02-05 21:11 ` John Cowan
2020-02-05 22:42 ` szgyg
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=99218b8d8f572c8748963924e82d265652487a09@webmail \
--to=dsmich@roadrunner.com \
--cc=39118@debbugs.gnu.org \
--cc=cowan@ccil.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).