From: <dsmich@roadrunner.com>
To: guile-devel@gnu.org, Andy Wingo <wingo@pobox.com>
Subject: Re: guile 3 update, june 2018 edition
Date: Fri, 29 Jun 2018 20:40:02 -0400 [thread overview]
Message-ID: <20180630004002.MNG3L.93631.root@cdptpa-web09> (raw)
In-Reply-To: <871scq2env.fsf@pobox.com>
Greetings Andy!
---- Andy Wingo <wingo@pobox.com> wrote:
> Hi,
>
> Just wanted to give an update on Guile 3 developments. Last note was
> here:
>
> https://lists.gnu.org/archive/html/guile-devel/2018-04/msg00004.html
>
> The news is that the VM has been completely converted over to call out
> to the Guile runtime through an "intrinsics" vtable. For some
> intrinsics, the compiler will emit specialized call-intrinsic opcodes.
> (There's one of these opcodes for each intrinsic function type.) For
> others that are a bit more specialized, like the intrinsic used in
> call-with-prompt, the VM calls out directly to the intrinsic.
Very exciting!
However, master is not building for me. :(
git clean -dxf; ./autogen.sh && ./configure && make -j5
gives me
SNARF atomic.x
SNARF backtrace.x
SNARF boolean.x
In file included from atomic.c:29:0:
extensions.h:26:30: fatal error: libguile/libpath.h: No such file or directory
#include "libguile/libpath.h"
^
compilation terminated.
Makefile:3893: recipe for target 'atomic.x' failed
make[2]: *** [atomic.x] Error 1
Maybe some dependency tuning is needed?
So. Building without -j :
make clean; make
gives gives a segfault when generating the docs
SNARF regex-posix.doc
GEN guile-procedures.texi
Uncaught exception:
Backtrace:
/bin/bash: line 1: 13428 Broken pipe cat alist.doc array-handle.doc array-map.doc arrays.doc async.doc atomic.doc backtrace.doc boolean.doc bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc debug.doc deprecated.doc deprecation.doc dynl.doc dynwind.doc eq.doc error.doc eval.doc evalext.doc expand.doc extensions.doc fdes-finalizers.doc feature.doc filesys.doc fluids.doc foreign.doc fports.doc gc-malloc.doc gc.doc gettext.doc generalized-arrays.doc generalized-vectors.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc list.doc load.doc macros.doc mallocs.doc memoize.doc modules.doc numbers.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc promises.doc r6rs-ports.doc random.doc rdelim.doc read.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc srfi-1.doc srfi-4.doc srfi-13.doc srfi-14.doc srfi-60.doc stackchk.doc stacks.doc stime.doc strings.doc strorder.doc strports.doc struct.doc symbols.doc syntax.doc threads.doc throw.doc trees.doc unicode.doc uniform.doc values.doc variable.doc vectors.doc version.doc vports.doc weak-set.doc weak-table.doc weak-vector.doc dynl.doc posix.doc net_db.doc socket.doc regex-posix.doc
13429 Segmentation fault | GUILE_AUTO_COMPILE=0 ../meta/build-env guild snarf-check-and-output-texi > guile-procedures.texi
Makefile:3910: recipe for target 'guile-procedures.texi' failed
This is
$ git describe
v2.2.2-504-gb5dcdf2e2
And gcc is
$ gcc --version
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
On an up to date Debian 9.4 system:
$ uname -a
Linux debmetrix 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux
-Dale
next prev parent reply other threads:[~2018-06-30 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 8:13 guile 3 update, june 2018 edition Andy Wingo
2018-06-30 0:40 ` dsmich [this message]
2018-07-02 4:02 ` dsmich
2018-07-17 10:32 ` dsmich
2018-07-02 9:28 ` Ludovic Courtès
2018-07-05 17:05 ` Andy Wingo
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=20180630004002.MNG3L.93631.root@cdptpa-web09 \
--to=dsmich@roadrunner.com \
--cc=guile-devel@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).