From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Cc: Dwight <dcrs6000@aceweb.com>
Subject: Re: Unable to build guile
Date: Wed, 05 Nov 2008 10:10:29 +0100 [thread overview]
Message-ID: <87tzamy1ve.fsf@gnu.org> (raw)
In-Reply-To: 4910B219.9000301@aceweb.com
Hello,
Dwight <dcrs6000@aceweb.com> writes:
> (gdb) bt full
> #0 0xd004a864 in pthread_mutexattr_init () from /usr/lib/libpthreads.a(shr_xpg5.o)
> No symbol table info available.
> #1 0xd6dd0bac in scm_threads_prehistory (base=0x2ff21e48) at threads.c:1656
> No locals.
> #2 0xd6e38b40 in scm_i_init_guile (base=0x0) at init.c:421
It looks like `get_thread_stack_base ()' doesn't work.
Can you run "grep -i pthread_attr_getstack config.h" and "grep -i
pthread_get_stackaddr config.h" from the build directory?
> numbers.c: In function 'guile_ieee_init':
> numbers.c:622: warning: dereferencing type-punned pointer will break strict-aliasing rules
> numbers.c:645: warning: dereferencing type-punned pointer will break strict-aliasing rules
It's surprising that `DINFINITY' and `DQNAN' are declared as ints. Can
you "rgrep '\(DINFINITY\|DQNAN\)' /usr/include"?
Our code appears to be based on that of Octave
(http://hg.savannah.gnu.org/hgweb/octave/file/ec969f3b8955/liboctave/lo-ieee.cc),
which (erroneously) assumes that these variables are only used on OSF.
> net_db.c: In function 'scm_resolv_error':
> net_db.c:112: warning: implicit declaration of function 'hstrerror'
Can you also "rgrep hstrerror /usr/include"?
Thanks in advance,
Ludovic.
next prev parent reply other threads:[~2008-11-05 9:10 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 [this message]
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
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=87tzamy1ve.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).