From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: autocompilation support in master
Date: Fri, 05 Jun 2009 23:15:43 +0100 [thread overview]
Message-ID: <87d49ijpio.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87hbyujpof.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Fri\, 05 Jun 2009 23\:12\:16 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> ...
> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> ERROR: Stack overflow
>
> But if I switch to a shell and repeat with --debug, no problem:
>
> neil@arudy:~/SW/Guile/git/module$ GUILE_AUTO_COMPILE=0 GUILE_FLAGS=--debug ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> wrote `language/ecmascript/spec.go'
>
> And no problem if I now remove the --debug again:
>
> neil@arudy:~/SW/Guile/git/module$ GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> wrote `language/ecmascript/spec.go'
>
> Or even if I delete language/ecmascript/spec.go and retry (so it's not
> connected with spec.scm already having been compiled):
>
> neil@arudy:~/SW/Guile/git/module$ rm language/ecmascript/spec.go
> neil@arudy:~/SW/Guile/git/module$ GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> wrote `language/ecmascript/spec.go'
One more data point. If I now try `make' again, it fails a bit later
with compile-ghil:
...
Making all in module
make[2]: Entering directory `/home/neil/SW/Guile/git/module'
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/impl.go" "language/ecmascript/impl.scm"
wrote `language/ecmascript/impl.go'
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/base.go" "language/ecmascript/base.scm"
wrote `language/ecmascript/base.go'
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/function.go" "language/ecmascript/function.scm"
wrote `language/ecmascript/function.go'
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/array.go" "language/ecmascript/array.scm"
wrote `language/ecmascript/array.go'
GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "language/ecmascript/compile-ghil.go" "language/ecmascript/compile-ghil.scm"
ERROR: Stack overflow
Neil
next prev parent reply other threads:[~2009-06-05 22:15 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 [this message]
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
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=87d49ijpio.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--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).