[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: stack overflow / partial success

From: Rainer Tammer
Subject: Re: stack overflow / partial success
Date: Tue, 19 Feb 2008 08:15:40 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv: Gecko/20070326 Thunderbird/ Mnenhy/


Ludovic Courtès wrote:
So what does "grep inline config.log" show?!

There is a "inline" but this version is not compatible...

Note that this does not answer my question.  :-)

I know...
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

Yes, this is fixed in the forthcoming 1.8.4 (hopefully released later

This sounds great, then it should work without the __inline__ hack.
/* Define to 1 if you have the `hstrerror' function. */

Then you should only get a warning at compilation-time about
`hstrerror ()' being undeclared, but the build process should continue
and Guile should link fine.

I'm reluctant to adding a `#define _USE_IRS' without any compelling
reason, since (i) the leading underscore makes it look like an internal
macro, and (ii) I don't know what it's really supposed to do.

Yes and no,
IBM XL C/C++ continues but gcc 4.2.2 stops due to the -Wall switch...

gmake[3]: Entering directory `/daten/source/guile-1.8.3/libguile'
/usr/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror -MT net_db.lo -MD -MP -MF .deps/net_db.Tpo -c -o net_db.lo net_db.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror -MT net_db.lo -MD -MP -MF .deps/net_db.Tpo -c net_db.c -DPIC -o .libs/net_db.o
cc1: warnings being treated as errors
net_db.c: In function 'scm_resolv_error':
net_db.c:112: warning: implicit declaration of function 'hstrerror'

The easiest solution wold be an AIX note in the INSTALL:

n.1. AIX with IBM Compiler

n.2. AIX with gcc 4.x

and the setting for the extended stack "(debug-set! stack 80000)" should also be mention.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]