From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Subject: re: Guile 1.8 and 86_64 gcc 4
Date: Fri, 14 Apr 2006 07:31:35 -0700 [thread overview]
Message-ID: <20060414142356.M94903@ccrma.Stanford.EDU> (raw)
One more bit of info. The only change needed to get the build
to run to completion is to set SCM_DEBUG_CELL_ACCESSES to 1.
The resultant guile also runs without stack overflow.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-04-14 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 14:31 Bill Schottstaedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-14 15:58 Guile 1.8 and 86_64 gcc 4 Bill Schottstaedt
2006-04-14 18:18 Bill Schottstaedt
2006-04-15 0:57 ` Kevin Ryde
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=20060414142356.M94903@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
/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).