unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
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: Wed, 20 Feb 2008 09:18:52 +0100	[thread overview]
Message-ID: <47BBE26C.1020507@tammer.net> (raw)
In-Reply-To: <87zltwipe6.fsf@gnu.org>

Hello,

Ludovic Courtès wrote:
> Hi Rainer,
> [...}
>   
>> 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?  :-)
>   
I have tested the build with both compilers gcc 4.2.2 and IBM XL C/C++ 
9.0 on AIX 6.1.
I am planing to release a rpm package of GUILE for AIX so I have to test 
the build with
different compilers to decide which produces the best result :-))

> 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.
>
>   
This could avoid some warnings but ... with the warning on the code 
tends to be cleaner.
>> 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.
>
>   
I will test the new 1.8.4 release and I will make detailed notes about 
all (still ?) needed changes
for AIX 6.1. When I have finished this I will try this on AIX 5.3.

I also can provide build notes for the AIX platform.
> Thanks for your report!
>
> Ludovic.
>
>
>   
Bye
  Rainer





  reply	other threads:[~2008-02-20  8:18 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
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 [this message]
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=47BBE26C.1020507@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).