From: Hans Aberg <haberg-1@telia.com>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org
Subject: Re: GIT version: autocompiling startup file
Date: Fri, 21 Jan 2011 11:04:24 +0100 [thread overview]
Message-ID: <5EA77F96-7EA8-49D8-B8B6-D84D52D11334@telia.com> (raw)
In-Reply-To: <8CD870DF94E6CA5-E68-1D13C@Webmail-d124.sysops.aol.com>
On 21 Jan 2011, at 00:07, Mark Harig wrote:
>> 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.
I found the error:
On my computer, the directory ~/.cache/ had already been created by
another program, setting another owner so that guile could not create
its directories in it. Then, in the function compiled-file-name in
file system/base/compile.scm, the exception from ensure-writable-dir
is converted to #f, which is the argument after "string" in the error
message above.
By contrast, if it compiles, the location of the .go file is written
out.
next prev parent reply other threads:[~2011-01-21 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 23:07 GIT version: autocompiling startup file Mark Harig
2011-01-21 8:09 ` Hans Aberg
2011-01-21 8:32 ` Hans Aberg
2011-01-21 10:04 ` Hans Aberg [this message]
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=5EA77F96-7EA8-49D8-B8B6-D84D52D11334@telia.com \
--to=haberg-1@telia.com \
--cc=bug-guile@gnu.org \
--cc=idirectscm@aim.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).