From: Rainer Tammer <tammer@tammer.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: stack overflow / partial success
Date: Mon, 18 Feb 2008 15:00:35 +0100 [thread overview]
Message-ID: <47B98F83.6080700@tammer.net> (raw)
In-Reply-To: <87zltyr1mh.fsf@gnu.org>
Hello,
Ludovic Courtès wrote:
> Rainer Tammer <tammer@tammer.net> writes:
> [...]
>
>> Unfortunately no ...
>>
>
> So what does "grep inline config.log" show?!
>
>
There is a "inline" but this version is not compatible...
The "inline" produces the following error:
"strings.c", line 132.10: 1506-780 (S) Reference to "scm_double_cell"
with internal linkage is not allowed within inline definition of
"scm_i_take_stringbufn".
The inline keyword is only recognized under compilation with c99 or with
the -qlanglvl=stdc99 or -qlanglvl=extc99 options (or equivalent pragmas) or
-qkeyword=inline. Note that the latter option is enabled by default for
xlc in the configuration file that is shipped with the compiler. The
__inline__ keyword is
recognized at all language levels.
>
>> The -brtl dos the following:
>>
>
> OK, that's something Guile's `configure' should not worry about, I
> guess.
>
>
Yes,
the setting a "export LDFLAGS=-Wl,-brtl" before you call configure is
sufficient (and documented in the latest libtool 1.5.26 readme).
>>> There's only one place where `hstrerror ()' is used, and it's enclosed
>>> in `#if HAVE_STRERROR'.
>>>
>> Unfortunately HAVE_STRERROR is defined to 1 ...
>>
>
> Sorry, I really meant `HAVE_HSTRERROR' (with `H'), which must be
> undefined on AIX, right?
>
>
/* Define to 1 if you have the `hstrerror' function. */
#define HAVE_HSTRERROR 1
No, this is defined...
> Thanks,
> Ludovic.
>
>
Bye
Rainer
>
>
next prev parent reply other threads:[~2008-02-18 14:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 8:22 stack overflow Rainer Tammer
2008-02-13 9:05 ` Ludovic Courtès
2008-02-13 9:15 ` Ludovic Courtès
2008-02-13 11:46 ` Rainer Tammer
2008-02-13 12:49 ` Ludovic Courtès
2008-02-14 7:36 ` stack overflow / partial success Rainer Tammer
2008-02-14 8:38 ` Ludovic Courtès
2008-02-18 6:11 ` Rainer Tammer
2008-02-18 8:33 ` Ludovic Courtès
2008-02-18 9:56 ` Rainer Tammer
2008-02-18 10:37 ` Ludovic Courtès
2008-02-18 14:00 ` Rainer Tammer [this message]
2008-02-18 14:11 ` Ludovic Courtès
2008-02-19 7:15 ` Rainer Tammer
2008-02-19 21:53 ` Ludovic Courtès
2008-02-20 8:18 ` Rainer Tammer
2008-02-20 9:28 ` Rainer Tammer
2008-02-20 14:40 ` GUILE 1.8.4 on AIX 6.1 Rainer Tammer
[not found] ` <87wsp83807.fsf@ossau.uklinux.net>
[not found] ` <871w7fore8.fsf@gnu.org>
[not found] ` <66e540fe0802140226k3cd96c46x286ac753bbb2b8b7@mail.gmail.com>
[not found] ` <87ejbfg4pr.fsf@gnu.org>
[not found] ` <66e540fe0802140339n2121e1d9y85fcc9f019d8be0f@mail.gmail.com>
2008-02-25 21:52 ` stack overflow Neil Jerram
2008-07-16 12:34 ` Ludovic Courtès
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=47B98F83.6080700@tammer.net \
--to=tammer@tammer.net \
--cc=bug-guile@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).