From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Cc: Dwight <dcrs6000@aceweb.com>
Subject: Re: Unable to build guile
Date: Sun, 09 Nov 2008 22:48:05 +0100 [thread overview]
Message-ID: <87y6zsinai.fsf@gnu.org> (raw)
In-Reply-To: 4916328E.9090104@aceweb.com
Hello,
Dwight <dcrs6000@aceweb.com> writes:
>> Hmm, that's not very helpful. Could you try finding out what it is that
>> determines that the stack base is NULL?
> I do not understand what you are asking.
Hmm, can you try another thing in GDB:
b main
run -q -c 0
b scm_threads_prehistory
c
whatis scm_i_pthread_mutexattr_recursive
p scm_i_pthread_mutexattr_recursive
c
And again:
./libtool --mode=execute gdb ./libguile/guile -x the-new-script
Sorry but it's quite tedious to debug remotely. :-(
> # grep hstrerror /usr/include/*
> /usr/include/netdb.h:const char *hstrerror();
> /usr/include/netdb.h:const char * hstrerror(int);
Can you check whether these declarations are enclosed in an `#ifdef'?
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-11-09 21:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 21:08 Unable to build guile Dwight
2008-11-02 20:31 ` Ludovic Courtès
2008-11-03 21:01 ` Andy Wingo
[not found] ` <490E7842.9040903@aceweb.com>
[not found] ` <87d4hdmbw8.fsf@gnu.org>
[not found] ` <490F78C1.9020703@aceweb.com>
[not found] ` <87ljw01lm1.fsf@gnu.org>
2008-11-04 2:16 ` Dwight
2008-11-04 11:11 ` Ludovic Courtès
2008-11-04 20:35 ` Dwight
2008-11-05 9:10 ` Ludovic Courtès
2008-11-05 21:17 ` Dwight
2008-11-06 11:28 ` Ludovic Courtès
2008-11-07 1:22 ` Dwight
2008-11-08 17:49 ` Ludovic Courtès
2008-11-09 0:45 ` Dwight
2008-11-09 21:48 ` Ludovic Courtès [this message]
2008-11-10 2:26 ` Dwight
2008-11-04 17:50 ` Marijn Schouten (hkBst)
2008-11-05 8:42 ` Ludovic Courtès
2008-11-05 15:05 ` Marijn Schouten (hkBst)
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=87y6zsinai.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
--cc=dcrs6000@aceweb.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).