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 10:28:50 +0100 [thread overview]
Message-ID: <47BBF2D2.6050701@tammer.net> (raw)
In-Reply-To: <87zltwipe6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
Hello Ludovic,
Ludovic Courtès wrote:
> Hi Rainer,
> [...]
>
> 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.
>
>
The 1.8.4 release looks good but I had to tweak two little things:
1. guile-readline
./guile-readline/config.guess -> this file was not refreshed ...
./guile-readline/config.sub -> this file was not refreshed ...
I solved this by copying the two files from the ./guile-1.8.4 base dir
to guile-libreadline
2. gc_os_dep.c
*** gc_os_dep.c 2008-02-20 09:42:18.000000000 +0100
--- /daten/source/guile-1.8.4/libguile/gc_os_dep.c 2008-02-16
19:50:24.000000000 +0100
***************
*** 1159,1165 ****
# endif
# endif
! # if defined(IA64) && !defined(RS6000)
# define MACH_TYPE "IA64"
# define ALIGN_DOUBLE
/* Requires 16 byte alignment for malloc */
--- 1159,1165 ----
# endif
# endif
! # ifdef IA64
# define MACH_TYPE "IA64"
# define ALIGN_DOUBLE
/* Requires 16 byte alignment for malloc */
This avoids some redefinitions (MACH_TYPE, ..).
I have used the following compiler settings with IBM XL C/C++:
.guile
(debug-set! stack 160000)
configure.aix
#!/usr/bin/bash
export CONFIG_SHELL=/usr/bin/bash
export CONFIG_ENV_ARGS=/usr/bin/bash
export CC=cc_r
export CXX=xlC_r
export PATH=/opt/freeware/bin:$PATH
export LDFLAGS="-Wl,-brtl -L/opt/freeware/lib"
export CFLAGS="-D_USE_IRS -Dinline=__inline__ -qtune=auto -O2
-I/opt/freeware/include"
./configure --enable-dynamic-linking --prefix=/opt/freeware
--enable-shared --disable-static
gmake > make.log
gmake check > check.log
I have attached the check results to this post.
> Thanks for your report!
>
> Ludovic.
>
>
>
Bye
Rainer
[-- Attachment #2: check-log-aix-1.8.4.zip --]
[-- Type: application/zip, Size: 99981 bytes --]
next prev parent reply other threads:[~2008-02-20 9:28 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
2008-02-20 9:28 ` Rainer Tammer [this message]
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=47BBF2D2.6050701@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).