From: <dsmich@roadrunner.com>
To: Neil Jerram <neil@ossau.uklinux.net>, Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: autocompilation support in master
Date: Tue, 9 Jun 2009 6:31:11 -0400 [thread overview]
Message-ID: <20090609103112.G0G6X.15879.root@cdptpa-web23-z01> (raw)
In-Reply-To: <20090609005226.GA3468@fibril.netris.org>
---- Mark H Weaver <mhw@netris.org> wrote:
> On Tue, Jun 09, 2009 at 12:24:48AM +0100, Neil Jerram wrote:
> > > GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> > > ERROR: Stack overflow
> >
> > This is still happening for me after pulling the latest master today.
>
> I have the same problem on Debian Lenny/x86, and am able to work
> around it by increasing the stack size resource limit. On my system,
> "ulimit -s 16384" (within bash) before running "make" does the trick.
> Unfortunately, this is not a portable solution.
Yes, I've experienced this too. Works for me when I bump up my stack to 9000 from 8192.
I've also found that's it's compiler dependent. Gcc 4.4 works I think, while 4.3 fails. (Not sure about that, as I'm not at that machine right now).
-Dale
>
> Mark
>
>
next prev parent reply other threads:[~2009-06-09 10:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 22:07 autocompilation support in master Andy Wingo
2009-06-05 22:12 ` Neil Jerram
2009-06-05 22:15 ` Neil Jerram
2009-06-08 23:24 ` Neil Jerram
2009-06-09 0:52 ` Mark H Weaver
2009-06-09 7:27 ` Andy Wingo
2009-06-09 18:47 ` Mark H Weaver
2009-06-09 21:39 ` Andy Wingo
2009-06-10 2:39 ` Mark H Weaver
2009-06-11 21:50 ` Neil Jerram
2009-06-10 3:39 ` Mark H Weaver
2009-06-10 4:11 ` Mark H Weaver
2009-06-10 4:29 ` Mark H Weaver
2009-06-11 22:23 ` Neil Jerram
2009-06-09 10:31 ` dsmich [this message]
2009-06-06 13:19 ` Ludovic Courtès
2009-06-06 23:43 ` Andy Wingo
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=20090609103112.G0G6X.15879.root@cdptpa-web23-z01 \
--to=dsmich@roadrunner.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=neil@ossau.uklinux.net \
--cc=wingo@pobox.com \
/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).