From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Cc: Dwight <dcrs6000@aceweb.com>
Subject: Re: Unable to build guile
Date: Thu, 06 Nov 2008 12:28:03 +0100 [thread overview]
Message-ID: <87iqr1t7p8.fsf@gnu.org> (raw)
In-Reply-To: 49120D5C.8040903@aceweb.com
Hello,
Dwight <dcrs6000@aceweb.com> writes:
> # grep -i pthread_attr_getstack config.h
> /* Define to 1 if you have the `pthread_attr_getstack' function. */
> #define HAVE_PTHREAD_ATTR_GETSTACK 1
> /* #undef PTHREAD_ATTR_GETSTACK_WORKS */
>
> # grep -i pthread_get_stackaddr config.h
> /* Define to 1 if you have the `pthread_get_stackaddr_np' function. */
> /* #undef HAVE_PTHREAD_GET_STACKADDR_NP */
Can you try out the following GDB script:
b main
run -q -c 0
b get_thread_stack_base
c
b scm_get_stack_base
c
finish
finish
quit
Save it to a file, say `the-script', `cd' to the top build directory and
run:
./libtool --mode=execute gdb ./libguile/guile -x the-script
Then you can post the GDB output here.
The goal is to understand which part of the code is used to determine
the stack base, and what it returns.
> # grep -E "DINFINITY|DQNAN" *
> float.h:#define DINFINITY _DBLINF
> float.h: extern unsigned int DQNAN[2];
> float.h:#define DBL_QNAN (*((double *) (DQNAN)))
> math.h:#define DINFINITY _DBLINF
OK, they are truly declared as ints, which truly breaks strict aliasing
rules. Then we should either compile that file with
`-fno-strict-aliasing' or not use `-Werror'.
>> 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.
> AIX is supposed to be compliant with the latest OSF specifications!
> If you like you can check out the link below to get more information
> about AIX compatability/compliance with UNIX standards.
>
> http://www-03.ibm.com/systems/p/os/aix/standards/index.html
I am roughly assuming OSF == Tru64 (aka. OSF/1). I don't see "OSF"
listed in the above page. According to
http://en.wikipedia.org/wiki/Open_Software_Foundation, OSF is was merged
with the Open Group.
Anyway, do you have pointers to documentation or standards that describe
`DQNAN' and `DINFINITY'? I don't see anything like this at
opengroup.org.
>>>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"?
> 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?
Thank you!
Ludo'.
next prev parent reply other threads:[~2008-11-06 11:28 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 [this message]
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=87iqr1t7p8.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).