unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Greg Troxel <gdt@lexort.com>
Cc: guile-user@gnu.org
Subject: Re: guile 2.0 and slib build procedure: cache bug?
Date: Fri, 11 Mar 2022 19:50:34 +0100	[thread overview]
Message-ID: <CAA2Xvw+Sg9pzHmTAnkT98x39XEeFgmAjzcb29oT12=o7oVAxNg@mail.gmail.com> (raw)
In-Reply-To: <rmia6dxjm2b.fsf@s1.lexort.com>

Hi Greg!

The procedure module-export-all! was introduced in 2.0.1.

It appears that the guile.init (which is distributed with slib, not guile)
which you are using requires guile 2.0.1.

Best regards,
Mikael

On Fri, Mar 11, 2022 at 2:56 AM Greg Troxel <gdt@lexort.com> wrote:

>
> Yes, I know guile 2.0 is old.  However, in a packaging system there are
> programs that still need 2.2, some that need 2.0, and then there is
> lilypond, documented to need 1.8.   So in pkgsrc we are trying to cope
> with 4 versions.
>
> For slib, today we have two versions, for 2.0 and 2.2 (just because 3.0
> is newly arrived in pkgsrc after resolving problems with pax and JIT).
>
>
> For the guile 2.0 slib package, it mostly works, and builds slibcat at
> package time in a chroot and then the package installs that fine.
>
> If I start guile and (use-modules (ice-9 slib)), it compiles two files
> and produces:
>
>   $ ls -l .cache/guile/ccache/2.0-LE-8-2.0/usr/pkg/share/slib/
>   total 52
>   -rw-r--r--  1 gdt  users  30382 Mar 10 20:40 guile.init.go
>   -rw-r--r--  1 gdt  users  16900 Mar 10 20:40 require.scm.go
>
> which all looks fine.    I can start guile and do it again.
>
> But then, if I try to build the slib package, I get a failure, below.
> If I remove these two cached files, the program runs.
>
> The error is a complaint abotu module-export-all! being unbound.
>
>
> Again, I know guile 2.0 is unsupported and probably nobody cares, but I
> thought it would be useful to point this out and perhaps someone has a
> clue.
>
> In the meantime I'll try to wave my magic wand again and get all the
> upstreams of guile-using packages that don't work with 3.0 to have a new
> stable, formal release that works with 3.0 :-)
>
> Thanks,
> Greg (a guile user since probably the 90s)
>
>
>
>
>
> => Creating installation directories
> /bin/rm -f
> /tmp/work/devel/guile-slib/work/.destdir/usr/pkg/guile/2.0/share/guile/site/2.0/slib
> /bin/ln -sf /usr/pkg/share/slib
> /tmp/work/devel/guile-slib/work/.destdir/usr/pkg/guile/2.0/share/guile/site/2.0/slib
> /bin/rm -f
> /tmp/work/devel/guile-slib/work/.destdir/usr/pkg/guile/2.0/share/guile/site/2.0/slibcat
> cd
> /tmp/work/devel/guile-slib/work/.destdir/usr/pkg/guile/2.0/share/guile/site/2.0/slib
> &&  GUILE_LOAD_PATH=/usr/pkg/share
> GUILE_IMPLEMENTATION_PATH=/tmp/work/devel/guile-slib/work/.destdir/usr/pkg/guile/2.0/share/guile/site/2.0
> /usr/pkg/guile/2.0/bin/guile -q -c "(begin (use-modules (ice-9 slib))
> (require 'new-catalog))"
> Backtrace:
> In ice-9/command-line.scm:
>  181: 19 [#<procedure 72d4b53644a0 at ice-9/command-line.scm:176:6 (port)>
> #<input: string 72d4b5b6c4e0>]
> In unknown file:
>    ?: 18 [eval (begin # #) #<directory # 72d4b56fe960>]
> In ice-9/eval.scm:
>  505: 17 [#<procedure 72d4b5b11720 at ice-9/eval.scm:499:4 (exp)> (begin #
> #)]
> In ice-9/psyntax.scm:
> 1107: 16 [expand-top-sequence ((begin (use-modules #) (require #))) () ...]
>  990: 15 [scan ((begin (use-modules #) (require #))) () ...]
>  990: 14 [scan ((use-modules (ice-9 slib)) (require (quote new-catalog)))
> () ...]
>  279: 13 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...]
> In ice-9/boot-9.scm:
> 3622: 12 [process-use-modules (((ice-9 slib)))]
>  712: 11 [map #<procedure 72d4b56bb260 at ice-9/boot-9.scm:3622:25
> (mif-args)> ((#))]
> 3623: 10 [#<procedure 72d4b56bb260 at ice-9/boot-9.scm:3622:25 (mif-args)>
> (#)]
> 2900: 9 [resolve-interface (ice-9 slib) #:select ...]
> 2825: 8 [#<procedure 72d4b56b2ac0 at ice-9/boot-9.scm:2813:4 (name
> #:optional autoload version #:key ensure)> # ...]
> 3101: 7 [try-module-autoload (ice-9 slib) #f]
> 2412: 6 [save-module-excursion #<procedure 72d4b5381630 at
> ice-9/boot-9.scm:3102:17 ()>]
> 3121: 5 [#<procedure 72d4b5381630 at ice-9/boot-9.scm:3102:17 ()>]
> In unknown file:
>    ?: 4 [primitive-load-path "ice-9/slib" ...]
> In ice-9/boot-9.scm:
> 1734: 3 [%start-stack load-stack ...]
> 1739: 2 [#<procedure 72d4b5381540 ()>]
> In unknown file:
>    ?: 1 [primitive-load-path "slib/guile.init"]
> In /usr/pkg/guile/2.0/share/guile/site/2.0/slib/guile-2.init:
>  174: 0 [#<procedure 72d4b5395b00 ()>]
>
> /usr/pkg/guile/2.0/share/guile/site/2.0/slib/guile-2.init:174:0: In
> procedure #<procedure 72d4b5395b00 ()>:
> /usr/pkg/guile/2.0/share/guile/site/2.0/slib/guile-2.init:174:0: In
> procedure module-lookup: Unbound variable: module-export-all!
> *** Error code 1
>


  reply	other threads:[~2022-03-11 18:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  1:49 guile 2.0 and slib build procedure: cache bug? Greg Troxel
2022-03-11 18:50 ` Mikael Djurfeldt [this message]
2022-03-11 20:05   ` Greg Troxel

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='CAA2Xvw+Sg9pzHmTAnkT98x39XEeFgmAjzcb29oT12=o7oVAxNg@mail.gmail.com' \
    --to=mikael@djurfeldt.com \
    --cc=gdt@lexort.com \
    --cc=guile-user@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).