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:12:16 +0100 [thread overview]
Message-ID: <87hbyujpof.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3vdndc6os.fsf@pobox.com> (Andy Wingo's message of "Thu\, 04 Jun 2009 00\:07\:31 +0200")
Andy Wingo <wingo@pobox.com> writes:
> There's a lot of trickiness to this, but I think we all have instincts
> on how this should work. I'll write docs soon, but in the meantime, I
> would like for folks to ignore the implementation, and just use Guile
> for a while, and see if what it does sounds right to you. It prints some
> status info on the console when autocompiling.
Unfortunately I'm not getting through `make' yet:
...
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'
What's the explanation for that?
Neil
next prev parent reply other threads:[~2009-06-05 22:12 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 [this message]
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
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=87hbyujpof.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).