unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Hans Aberg <haberg-1@telia.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: GIT version: autocompiling startup file
Date: Thu, 27 Jan 2011 00:54:54 +0100	[thread overview]
Message-ID: <ECF588BB-5F0D-4C33-A0C3-D4098ECD3FB3@telia.com> (raw)
In-Reply-To: <m3ei7zcqxi.fsf@unquote.localdomain>

On 26 Jan 2011, at 22:10, Andy Wingo wrote:

>>>> When starting with 'guile -l', autocompiling fails, even with an
>>>> empty file.
>>>>
>> 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.
>
> Thanks for the detailed report.  I believe I've fixed this in git to
> give a more sensible error.

On Mac OS X, there are two locations for cached objects; when put  
there, the system will assume they can be regenerated and not be  
backed up. These would be
   ~/Library/Caches/Guile/
   /Library/Caches/Guile/
if keeping to Mac tradition using uppercase names. One can also mark  
~/.cache/ to be the same kind of area.




  reply	other threads:[~2011-01-26 23:54 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
2011-01-26 21:10   ` Andy Wingo
2011-01-26 23:54     ` Hans Aberg [this message]
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=ECF588BB-5F0D-4C33-A0C3-D4098ECD3FB3@telia.com \
    --to=haberg-1@telia.com \
    --cc=bug-guile@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).