From: Andy Wingo <wingo@pobox.com>
To: Marco Maggi <marco.maggi-ipsu@poste.it>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 fails to build without threads
Date: Fri, 20 May 2011 11:37:45 +0200 [thread overview]
Message-ID: <m34o4pyaom.fsf@unquote.localdomain> (raw)
In-Reply-To: <87hb9d4o8n.fsf@rapitore.luna> (Marco Maggi's message of "Mon, 02 May 2011 08:20:56 +0200")
On Mon 02 May 2011 08:20, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
> Andy Wingo wrote:
>>> stack size (kbytes, -s) 8192
>>
>> This should be quite large enough. If you are still
>> interested in debugging this issue, can you "call
>> scm_stack_report ()" in gdb from the scm_ithrow?
>
> Breakpoint 1, 0xb7f4fa80 in scm_ithrow ()
> from /home/marco/src/devel/scheme/checkouts/guile/libguile/.libs/libguile-2.0.so.22
> (gdb) call scm_stack_report()
> fffffd7c of stack: 0xbfffe268 - 0xbfffe008
Thanks. You seem to be running on system in which the stack grows up.
Is that the case? Check libguile/scmconfig.h and config.log.
You mention in your original report:
In the stable-2.0 branch I do:
$ git clean -dxf
$ ./autogen.sh
$ ./configure \
--prefix=3D/usr/local \
--enable-shared --disable-static \
CFLAGS=3D'-O3 -march=3Di686 -mtune=3Di686'
Are the "3D" things an artifact of some mailing list encoding thing, or
are they a mis-paste?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-20 9:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 14:47 guile-2.0.0 fails to build without threads Marijn
2011-04-11 16:19 ` Andy Wingo
2011-04-12 7:26 ` Marijn
2011-04-13 10:05 ` Andy Wingo
2011-04-13 13:44 ` Marijn
2011-04-13 14:09 ` Andy Wingo
2011-04-13 14:27 ` Marijn
2011-04-13 15:22 ` Andy Wingo
2011-04-14 13:25 ` Marijn
2011-04-28 11:17 ` Andy Wingo
2011-04-28 13:08 ` Ludovic Courtès
2011-04-28 13:15 ` Andy Wingo
2011-04-28 15:09 ` Ludovic Courtès
2011-05-03 14:58 ` Marijn
2011-05-04 12:19 ` Ludovic Courtès
2011-05-05 8:04 ` Marijn
2011-05-05 12:08 ` Ludovic Courtès
2011-05-05 13:59 ` Marijn
2011-05-05 14:25 ` Ludovic Courtès
2011-05-06 8:16 ` Marijn
2011-05-06 9:52 ` Ludovic Courtès
2011-05-06 12:49 ` Marijn
2011-05-10 7:43 ` Marijn
2011-05-03 14:55 ` Marijn
2011-04-12 6:49 ` Marco Maggi
2011-04-13 9:04 ` Marco Maggi
2011-04-13 11:42 ` Marco Maggi
2011-04-13 12:26 ` Andy Wingo
2011-04-13 13:56 ` Marco Maggi
2011-04-28 11:21 ` Andy Wingo
2011-05-02 6:20 ` Marco Maggi
2011-05-20 9:37 ` Andy Wingo [this message]
2011-05-20 18:41 ` Marco Maggi
2011-05-21 2:23 ` Mark H Weaver
2011-05-21 8:45 ` Andy Wingo
2011-05-21 13:51 ` Marco Maggi
2011-05-21 14:29 ` Neil Jerram
2011-06-17 10:25 ` Andy Wingo
2011-06-20 8:06 ` Andy Wingo
2011-06-22 21:39 ` Neil Jerram
2011-04-13 9:55 ` Andy Wingo
2011-04-13 14:19 ` Marco Maggi
2011-04-13 21:57 ` 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=m34o4pyaom.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=marco.maggi-ipsu@poste.it \
/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).