From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Cc: Dwight <dcrs6000@aceweb.com>
Subject: Re: Unable to build guile
Date: Sat, 08 Nov 2008 18:49:19 +0100 [thread overview]
Message-ID: <87fxm2az1c.fsf@gnu.org> (raw)
In-Reply-To: 4913983F.2090204@aceweb.com
Hello,
Dwight <dcrs6000@aceweb.com> writes:
> Breakpoint 1, main (argc=4, argv=0x2ff22058) at guile.c:72
> 72 guile.c: A file or directory in the path name does not exist..
> in guile.c
> Function "get_thread_stack_base" not defined.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xd004a864 in pthread_mutexattr_init () from /usr/lib/libpthreads.a(shr_xpg5.o)
> Breakpoint 2 at 0xd6c70efc: file gc_os_dep.c, line 1937.
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> The program no longer exists.
> /tmp/VIM/guile-1.8.5/the-script:7: Error in sourced command file:
> The program is not running.
> (gdb) quit
Hmm, that's not very helpful. Could you try finding out what it is that
determines that the stack base is NULL?
Alternatively, if you know of a way we could test Guile on that
platform, that would be great.
>>> I did a grep on /usr/include and /usr/include/sys
>>>
>>># grep hstrerror *
>>>netdb.h:const char *hstrerror();
>>>netdb.h:const char * hstrerror(int);
>>
>>
>> Is that under /usr/include or /usr/include/sys?
> Yes!
I mean, was it /usr/include/netdb.h or /usr/include/sys/netdb.h?
I assume the latter since <netdb.h> is already included in `net_db.c'.
Thanks for your perseverance!
Ludo'.
next prev parent reply other threads:[~2008-11-08 17:49 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 [this message]
2008-11-09 0:45 ` Dwight
2008-11-09 21:48 ` Ludovic Courtès
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=87fxm2az1c.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).