[r6rs] misc problems with the cache of precompiled files

[r6rs] misc problems with the cache of precompiled files

[Marco Maggi]

I just noticed that my cache has this file in it:

/home/marco/.cache/guile/ccache/2.0-0.Q-LE-4/home/marco/.cache/guile/ccache/2.0-0.Q-LE-4/home/marco/var/tmp/proof.sps.go.go

should  I expect this  or is  something wrong  with pathname
construction?  I  have not found  a way to reproduce  it for
now.

  Anyway, I have this script "proof.sps":

    (import (rnrs))
    (display "ciao\n")

first I do:

  $ rm -fr ~/.cache/guile/ccache/2.0-0.Q-LE-4/home/marco

to start from a clean state, then:

  $ guile -s proof.sps
  ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
  ;;;       or pass the --no-autocompile argument to disable.
  ;;; compiling proof.sps
  WARNING: (rnrs): `i/o-error-port' imported from both (rnrs files) and (rnrs io simple)
  WARNING: (rnrs): `i/o-port-error?' imported from both (rnrs files) and (rnrs io simple)
  ... <many more like this>
  ;;; compiled /home/marco/.cache/guile/ccache/2.0-0.Q-LE-4/home/marco/var/tmp/proof.sps.go
  ciao

  $ guile -s proof.sps
  ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
  ;;;       or pass the --no-autocompile argument to disable.
  ;;; compiling /usr/local/share/guile/2.0/srfi//srfi-11.scm
  ;;; WARNING: compilation of /usr/local/share/guile/2.0/srfi//srfi-11.scm failed:
  ;;; key misc-error, throw_args (#f "~A ~S" ("no code for module" (srfi srfi-11)) #f)
  ;;; compiling /usr/local/share/guile/2.0/rnrs/io//ports.scm
  ;;; WARNING: compilation of /usr/local/share/guile/2.0/rnrs/io//ports.scm failed:
  ;;; key misc-error, throw_args (#f "~A ~S" ("no such language" scheme) #f)
  ERROR: Unbound variable: define-module

-- 
Marco Maggi

Re: [r6rs] misc problems with the cache of precompiled files

[Marco Maggi]

"Marco Maggi" wrote:
> I just noticed that my cache has this file in it:

Sorry, I forgot: i686-pc-linux-gnu, guile 1.9.11.
-- 
Marco Maggi

Re: [r6rs] misc problems with the cache of precompiled files

[Andy Wingo]

Hello Marco,

On Fri 11 Jun 2010 08:04, Marco Maggi <marco.maggi-ipsu@poste.it> writes:

> I just noticed that my cache has this file in it:
>
> /home/marco/.cache/guile/ccache/2.0-0.Q-LE-4/home/marco/.cache/guile/ccache/2.0-0.Q-LE-4/home/marco/var/tmp/proof.sps.go.go
>
> should  I expect this  or is  something wrong  with pathname
> construction?

It doesn't look right. Let us know if you can reproduce it.

By the way, thank you for your bug reports, they have been good. I
haven't been able to get around to them all yet. You should build from
git, though, as there have been a number of bugs fixed since the
release.

>   Anyway, I have this script "proof.sps":
>
>     (import (rnrs))
>     (display "ciao\n")

There are some bugs still around regarding the compilation cache and
r6rs modules -- or specifically, with versioned modules, which r6rs
modules are. We're still working that one out and hpe to have something
in a couple days.

>   WARNING: (rnrs): `i/o-error-port' imported from both (rnrs files) and (rnrs io simple)
>   WARNING: (rnrs): `i/o-port-error?' imported from both (rnrs files) and (rnrs io simple)
>   ... <many more like this>

These warnings will be fixed soon.

Andy
-- 
http://wingolog.org/

Re: [r6rs] misc problems with the cache of precompiled files

[No Itisnt]

> There are some bugs still around regarding the compilation cache and
> r6rs modules -- or specifically, with versioned modules, which r6rs
> modules are. We're still working that one out and hpe to have something
> in a couple days.

Is that the issue I bumped into with (rnrs control)?

Re: [r6rs] misc problems with the cache of precompiled files

[Andy Wingo]

On Mon 14 Jun 2010 23:56, No Itisnt <theseaisinhere@gmail.com> writes:

>> There are some bugs still around regarding the compilation cache and
>> r6rs modules -- or specifically, with versioned modules, which r6rs
>> modules are. We're still working that one out and hpe to have something
>> in a couple days.
>
> Is that the issue I bumped into with (rnrs control)?

Can you refresh my memory? :)

A
-- 
http://wingolog.org/

Re: [r6rs] misc problems with the cache of precompiled files

[No Itisnt]

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Mon, Jun 14, 2010 at 6:00 PM, Andy Wingo <wingo@pobox.com> wrote:
> On Mon 14 Jun 2010 23:56, No Itisnt <theseaisinhere@gmail.com> writes:
>
>>> There are some bugs still around regarding the compilation cache and
>>> r6rs modules -- or specifically, with versioned modules, which r6rs
>>> modules are. We're still working that one out and hpe to have something
>>> in a couple days.
>>
>> Is that the issue I bumped into with (rnrs control)?
>
> Can you refresh my memory? :)

We talked about it in the Lua thread but I don't think you were able
to duplicate it.

Test case attached. (running it directly twice from the command line
causes an unresolved variable error that doesn't make sense)

[-- Attachment #2: test.scm --]
[-- Type: application/octet-stream, Size: 151 bytes --]

(define-module (module)
  #:use-module ((rnrs control) #:version (6))
  #:use-module (language tree-il))

(make-const #f 2)

(display 'done)
(newline)

Re: [r6rs] misc problems with the cache of precompiled files

[Andy Wingo]

On Tue 15 Jun 2010 23:41, No Itisnt <theseaisinhere@gmail.com> writes:

> On Mon, Jun 14, 2010 at 6:00 PM, Andy Wingo <wingo@pobox.com> wrote:
>> On Mon 14 Jun 2010 23:56, No Itisnt <theseaisinhere@gmail.com> writes:
>>
>>>> There are some bugs still around regarding the compilation cache and
>>>> r6rs modules -- or specifically, with versioned modules, which r6rs
>>>> modules are. We're still working that one out and hpe to have something
>>>> in a couple days.
>>>
>>> Is that the issue I bumped into with (rnrs control)?
>>
>> Can you refresh my memory? :)
>
> We talked about it in the Lua thread but I don't think you were able
> to duplicate it.
>
> Test case attached. (running it directly twice from the command line
> causes an unresolved variable error that doesn't make sense)

I can reproduce this now, for whatever reason:

$ meta/guile test.scm
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-autocompile argument to disable.
;;; compiling /home/wingo/src/guile/module/srfi/srfi-11.scm
;;; WARNING: compilation of /home/wingo/src/guile/module/srfi/srfi-11.scm failed:
;;; key misc-error, throw_args (#f "~A ~S" ("no code for module" (srfi srfi-11)) #f)
ERROR: In procedure module-lookup:
ERROR: Unbound variable: make-const

Bleah.

A
-- 
http://wingolog.org/

Re: [r6rs] misc problems with the cache of precompiled files

[No Itisnt]

On Tue, Jun 15, 2010 at 5:10 PM, Andy Wingo <wingo@pobox.com> wrote:
> On Tue 15 Jun 2010 23:41, No Itisnt <theseaisinhere@gmail.com> writes:
>
>> On Mon, Jun 14, 2010 at 6:00 PM, Andy Wingo <wingo@pobox.com> wrote:
>>> On Mon 14 Jun 2010 23:56, No Itisnt <theseaisinhere@gmail.com> writes:
>>>
>>>>> There are some bugs still around regarding the compilation cache and
>>>>> r6rs modules -- or specifically, with versioned modules, which r6rs
>>>>> modules are. We're still working that one out and hpe to have something
>>>>> in a couple days.
>>>>
>>>> Is that the issue I bumped into with (rnrs control)?
>>>
>>> Can you refresh my memory? :)
>>
>> We talked about it in the Lua thread but I don't think you were able
>> to duplicate it.
>>
>> Test case attached. (running it directly twice from the command line
>> causes an unresolved variable error that doesn't make sense)
>
> I can reproduce this now, for whatever reason:
>
> $ meta/guile test.scm
> ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;;       or pass the --no-autocompile argument to disable.
> ;;; compiling /home/wingo/src/guile/module/srfi/srfi-11.scm
> ;;; WARNING: compilation of /home/wingo/src/guile/module/srfi/srfi-11.scm failed:
> ;;; key misc-error, throw_args (#f "~A ~S" ("no code for module" (srfi srfi-11)) #f)
> ERROR: In procedure module-lookup:
> ERROR: Unbound variable: make-const
>
> Bleah.
>
> A
> --
> http://wingolog.org/

You couldn't get it before because it doesn't happen when you load it
with (use-modules), even on successive REPL sessions. Which just adds
confusion...