Andy Wingo <wi...@pobox.com> writes:
> Heya Neil,
Hi again! Apologies for the long hiatus... my home network imploded for
a while.
> It was an interesting analysis, though I admit I didn't follow all of
> it. The SIGPIPE didn't hit the subprocess because bash was doing
> something strange?
Yes, I think so. My interpretation of that email trail is that bash v3
doesn't let SIGPIPE get to its builtins, such as echo.
> How did your new test work out?
It worked. However, when I try to build Guile again now, to double
check, I get:
cat alist.doc arbiters.doc array-handle.doc array-map.doc arrays.doc async.doc
backtrace.doc boolean.doc bitvectors.doc bytevectors.doc chars.doc control.doc
continuations.doc debug.doc deprecated.doc deprecation.doc discouraged.doc
dynl.doc dynwind.doc eq.doc error.doc eval.doc evalext.doc expand.doc
extensions.doc feature.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 properties.doc r6rs-ports.doc random.doc
rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc
sort.doc srcprop.doc srfi-13.doc srfi-14.doc srfi-4.doc stackchk.doc stacks.doc
stime.doc strings.doc strorder.doc strports.doc struct.doc symbols.doc
threads.doc throw.doc trees.doc uniform.doc values.doc variable.doc vectors.doc
version.doc vports.doc weaks.doc dynl.doc filesys.doc posix.doc net_db.doc
socket.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; }
`scm_trampoline_1' is deprecated. Just use `scm_call_1' instead.
guile: uncaught throw to wrong-type-arg: (vm-debug-engine Wrong type to apply:
~S (#<with-fluids 404dc498>) (#<with-fluids 404dc498>))
Cannot exit gracefully when init is in progress; aborting.
cat: write error: Broken pipe
/bin/sh: line 1: 9771 Done(1) cat alist.doc arbiters.doc
array-handle.doc array-map.doc arrays.doc async.doc backtrace.doc boolean.doc
bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc
debug.doc deprecated.doc deprecation.doc discouraged.doc dynl.doc dynwind.doc
eq.doc error.doc eval.doc evalext.doc expand.doc extensions.doc feature.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 properties.doc r6rs-ports.doc random.doc rdelim.doc
read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc
srcprop.doc srfi-13.doc srfi-14.doc srfi-4.doc stackchk.doc stacks.doc
stime.doc strings.doc strorder.doc strports.doc struct.doc symbols.doc
threads.doc throw.doc trees.doc uniform.doc values.doc variable.doc vectors.doc
version.doc vports.doc weaks.doc dynl.doc filesys.doc posix.doc net_db.doc
socket.doc regex-posix.doc
9772 Aborted | GUILE_AUTO_COMPILE=0
../meta/uninstalled-env guile-tools snarf-check-and-output-texi >
guile-procedures.texi
Is that a known problem? Has the correct build incantation perhaps
changed (from './autogen.sh && ./configure && make && make check') ?
If I then go to a shell:
n...@arudy:~/SW/Guile/master$ GUILE_AUTO_COMPILE=0 ./meta/uninstalled-env guile
-c '(+ 3 3)'
`scm_trampoline_1' is deprecated. Just use `scm_call_1' instead.
guile: uncaught throw to wrong-type-arg: (vm-debug-engine Wrong type to apply:
~S (#<with-fluids b7adb498>) (#<with-fluids b7adb498>))
Cannot exit gracefully when init is in progress; aborting.
Aborted
So it's nothing specifically to do with 'guile-tools
snarf-check-and-output-texi'.
Also, in the autogen.sh step, in case it's relevant, I get some
warnings:
am/snarf:5: AM_V_SNARF_$(V: non-POSIX variable name
guile-readline/Makefile.am:22: `am/snarf' included from here
am/snarf:6: AM_V_SNARF_$(AM_DEFAULT_VERBOSITY: non-POSIX variable name
guile-readline/Makefile.am:22: `am/snarf' included from here
am/snarf:5: AM_V_SNARF_$(V: non-POSIX variable name
libguile/Makefile.am:22: `am/snarf' included from here
am/snarf:6: AM_V_SNARF_$(AM_DEFAULT_VERBOSITY: non-POSIX variable name
libguile/Makefile.am:22: `am/snarf' included from here
libguile/Makefile.am:664: AM_V_FILTER_$(V: non-POSIX variable name
libguile/Makefile.am:665: AM_V_FILTER_$(AM_DEFAULT_VERBOSITY: non-POSIX
variable name
am/guilec:33: AM_V_GUILEC_$(V: non-POSIX variable name
module/Makefile.am:22: `am/guilec' included from here
am/guilec:34: AM_V_GUILEC_$(AM_DEFAULT_VERBOSITY: non-POSIX variable name
module/Makefile.am:22: `am/guilec' included from here
am/snarf:5: AM_V_SNARF_$(V: non-POSIX variable name
srfi/Makefile.am:22: `am/snarf' included from here
am/snarf:6: AM_V_SNARF_$(AM_DEFAULT_VERBOSITY: non-POSIX variable name
srfi/Makefile.am:22: `am/snarf' included from here
am/snarf:5: AM_V_SNARF_$(V: non-POSIX variable name
test-suite/standalone/Makefile.am:22: `am/snarf' included from here
am/snarf:6: AM_V_SNARF_$(AM_DEFAULT_VERBOSITY: non-POSIX variable name
test-suite/standalone/Makefile.am:22: `am/snarf' included from here
Does that just mean I need to upgrade autotools?
Regards,
Neil
