[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
build failure after "eval is actually compile"
From: |
Ken Raeburn |
Subject: |
build failure after "eval is actually compile" |
Date: |
Wed, 26 Aug 2009 18:48:50 -0400 |
Building on GNU/Linux, with a fresh build tree, and without an
installed tree under $prefix, fails for me. I get:
./guile_filter_doc_snarfage --filter-snarfage) > regex-posix.doc ||
{ rm regex-posix.doc; false; }
cat alist.doc [...] regex-posix.doc | GUILE_AUTO_COMPILE=0 ../meta/
uninstalled-env guile-tools snarf-check-and-output-texi >
guile-procedures.texi || { rm guile-procedures.texi; false; }
ERROR: In procedure dynamic-link:
ERROR: file: "libguile-srfi-srfi-1-v-4", message: "libguile-srfi-
srfi-1-v-4.so: cannot open shared object file: No such file or
directory"
[...hit ^C here...]
make[3]: *** Deleting file `guile-procedures.texi'
make[3]: *** [guile-procedures.texi] Interrupt
This failure is caused because the srfi-1 code is needed before the
build has hit the srfi directory. (The need for hitting ^C is a
deadlock problem I'll describe in a separate message.) In slightly
older versions I would get:
;;; WARNING: compilation of /var/raeburn/guile/linux/meta/guile-tools
failed:
;;; key misc-error, throw_args ("dynamic-link" "file: ~S, message:
~S" ("libguile-srfi-srfi-1-v-4" "libguile-srfi-srfi-1-v-4.so: cannot
open shared object file: No such file or directory") #f)
... and then things would happily continue on. At least, until it
blew up somewhere else for unrelated reasons.
According to "git bisect", commit afe5e6b ("eval is actually compile")
is where this first comes up.
Ken
- build failure after "eval is actually compile",
Ken Raeburn <=