From: Mark Harig <idirectscm@aim.com>
To: bug-guile@gnu.org
Subject: Re: GIT version: autocompiling startup file
Date: Thu, 20 Jan 2011 18:07:41 -0500 [thread overview]
Message-ID: <8CD870DF94E6CA5-E68-1D13C@Webmail-d124.sysops.aol.com> (raw)
> When starting with 'guile -l', autocompiling fails, even with an
empty file.
>
> $ guile -l empty.scm
> ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;; or pass the --no-autocompile argument to disable.
> ;;; compiling empty.scm
> ;;; WARNING: compilation of empty.scm failed:
> ;;; key wrong-type-arg, throw_args ("dirname" "Wrong type argument in
position ~A (expecting ~A): ~S" (1 "string" #f) (#f))
> GNU Guile 1.9.14.68-a7d8a
This is not happening on my build of guile 1.9.14. Here is
the output of the above command:
$ rm empty.scm && touch empty.scm && guile -l empty.scm
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-autocompile argument to disable.
;;; compiling empty.scm
;;; compiled [long path to ]/empty.scm.go
GNU Guile 1.9.14
Copyright (C) 1995-2010 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)>
next reply other threads:[~2011-01-20 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 23:07 Mark Harig [this message]
2011-01-21 8:09 ` GIT version: autocompiling startup file Hans Aberg
2011-01-21 8:32 ` Hans Aberg
2011-01-21 10:04 ` Hans Aberg
2011-01-26 21:10 ` Andy Wingo
2011-01-26 23:54 ` Hans Aberg
2011-01-27 9:03 ` Andy Wingo
2011-01-27 13:33 ` Hans Aberg
-- strict thread matches above, loose matches on Subject: below --
2011-01-18 10:08 Hans Aberg
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=8CD870DF94E6CA5-E68-1D13C@Webmail-d124.sysops.aol.com \
--to=idirectscm@aim.com \
--cc=bug-guile@gnu.org \
/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).