From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ludo@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) Newsgroups: gmane.lisp.guile.bugs Subject: Re: stack overflow / partial success Date: Tue, 19 Feb 2008 22:53:53 +0100 Message-ID: <87zltwipe6.fsf@gnu.org> References: <47B2A8DF.9070004@tammer.net> <87tzkd8bvz.fsf@gnu.org> <87ejbh8ben.fsf@gnu.org> <47B2D88F.1040505@tammer.net> <87ir0tvx6e.fsf@inria.fr> <47B3EF9A.4090400@tammer.net> <87r6fgndap.fsf@gnu.org> <47B92174.5070300@tammer.net> <87ve4mu0ig.fsf@gnu.org> <47B95664.4070007@tammer.net> <87zltyr1mh.fsf@gnu.org> <47B98F83.6080700@tammer.net> <87bq6eqrqs.fsf@gnu.org> <47BA821C.5050503@tammer.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1203458453 7763 80.91.229.12 (19 Feb 2008 22:00:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Feb 2008 22:00:53 +0000 (UTC) To: bug-guile@gnu.org Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Tue Feb 19 23:01:18 2008 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JRaW4-0007q9-N0 for guile-bugs@m.gmane.org; Tue, 19 Feb 2008 23:00:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRaVZ-0007E1-Tv for guile-bugs@m.gmane.org; Tue, 19 Feb 2008 17:00:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JRaVU-0007C3-U4 for bug-guile@gnu.org; Tue, 19 Feb 2008 17:00:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JRaVT-00079o-Au for bug-guile@gnu.org; Tue, 19 Feb 2008 17:00:08 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRaVT-00079h-0Y for bug-guile@gnu.org; Tue, 19 Feb 2008 17:00:07 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JRaVS-0007WF-Ok for bug-guile@gnu.org; Tue, 19 Feb 2008 17:00:06 -0500 Original-Received: from root by ciao.gmane.org with local (Exim 4.43) id 1JRaVO-0003EF-L1 for bug-guile@gnu.org; Tue, 19 Feb 2008 22:00:02 +0000 Original-Received: from reverse-83.fdn.fr ([80.67.176.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Feb 2008 22:00:02 +0000 Original-Received: from ludo by reverse-83.fdn.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Feb 2008 22:00:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: reverse-83.fdn.fr X-Revolutionary-Date: 1 =?iso-8859-1?Q?Vent=F4se?= an 216 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEB1F5364 X-PGP-Key: http://www.laas.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 821D 815D 902A 7EAB 5CEE D120 7FBA 3D4F EB1F 5364 X-OS: i686-pc-linux-gnu User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) Cancel-Lock: sha1:lVxe1Jz05VyEXHES0TVe9QT4BEE= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:3804 Archived-At: Hi Rainer, Rainer Tammer writes: > Ludovic Courtès wrote: >> 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... I know for GCC but you said you were using xlc, right? :-) When compiling with GCC, you'd have to run `configure' with `--disable-error-on-warning' to avoid this problem---I'm wondering whether we should make it the default. > and the setting for the extended stack "(debug-set! stack 80000)" > should also be mention. Ah, so setting it fixed some problem? BTW, hopefully some of your problems are addressed by the newly-released 1.8.4. We'll look into the others (e.g., `strftime') for the next release. Thanks for your report! Ludovic.