Consider this source file: test.scm:
(use-modules (language python def) (system syntax internal) ((oop dict)
#:select (slask-it)))
(define-syntax m
(lambda (x)
(syntax-case x ()
((_ n m y)
(let* ((xx (syntax-expression x))
(yy (pk 'yy (source-properties xx)))
Hi,
I have a project I used to build with guile 2.2. I use the PKG_GUILE m4 macro
in my configure.ac. However, guile 3 comes with a guile.m4 whose PKG_GUILE only
checks for 2.2, 2.0 and 1.8, so configure fails.
Is this deprecated? Should I use something else to check for guile?
Thanks!
Julien Lepiller writes:
> I have a project I used to build with guile 2.2. I use the PKG_GUILE
> m4 macro in my configure.ac. However, guile 3 comes with a guile.m4
> whose PKG_GUILE only checks for 2.2, 2.0 and 1.8, so configure fails.
I use “GUILE_PKG([3.0 2.2])” in my code.
--
Ricardo
Hi there!
I'm not sure this is a bug report yet, but it may become one. I'm having
what looks like a Guile segfault issue for some Mac OS Mojave (10.14)
users. I've been packaging 64-bit Mac builds of LilyPond, which includes
libguile 1.8. The builds work well for myself and for nearly everyone e
