GIT version: autocompiling startup file

GIT version: autocompiling startup file

[Hans Aberg]

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

Re: GIT version: autocompiling startup file

[Mark Harig]

> 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)>

Re: GIT version: autocompiling startup file

[Hans Aberg]

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.

The problem is due to scm_from_latin1_symbol() in file load.c together  
with that I set the locale to LC_CTYPE=en_US.UTF-8. It works with  
either the default locale on Mac OS X 10.5.8, which is LC_CTYPE=UTF-8,  
or LC_CTYPE=en_US.ISO8859-1. However, some software does not work  
unless the locale is changed to what I set it to (the default locale  
causes problems).

Re: GIT version: autocompiling startup file

[Hans Aberg]

On 21 Jan 2011, at 09:09, Hans Aberg wrote:

> The problem is due to scm_from_latin1_symbol() in file load.c  
> together with that I set the locale to LC_CTYPE=en_US.UTF-8. It  
> works with either the default locale on Mac OS X 10.5.8, which is  
> LC_CTYPE=UTF-8, or LC_CTYPE=en_US.ISO8859-1. However, some software  
> does not work unless the locale is changed to what I set it to (the  
> default locale causes problems).

Actually, it does not compile with any of those locales. I tried though:
   (compile-file "empty.scm")
   ERROR: In procedure dirname:
   ERROR: Wrong type argument in position 1 (expecting string): #f

Re: GIT version: autocompiling startup file

[Hans Aberg]

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.

Re: GIT version: autocompiling startup file

[Andy Wingo]

On Fri 21 Jan 2011 11:04, Hans Aberg <haberg-1@telia.com> writes:

> On 21 Jan 2011, at 00:07, Mark Harig 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.

Cheers,

Andy
-- 
http://wingolog.org/

Re: GIT version: autocompiling startup file

[Hans Aberg]

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.

Re: GIT version: autocompiling startup file

[Andy Wingo]

On Thu 27 Jan 2011 00:54, Hans Aberg <haberg-1@telia.com> writes:

> 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.

You can set your XDG_CACHE_HOME to change this.  See
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
for more.

Andy
-- 
http://wingolog.org/

Re: GIT version: autocompiling startup file

[Hans Aberg]

On 27 Jan 2011, at 10:03, Andy Wingo wrote:

>> 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.
>
> You can set your XDG_CACHE_HOME to change this.  See
> http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
> for more.

This works. Put my .profile file
   export XDG_CACHE_HOME=$HOME/Library/Caches/XDG
as to not clutter Caches/.

If Guile wants to set its own on Mac OS X, then it might be
   $HOME/Library/Caches/Guile