Re: [PATCH] Fix hanging of popen.test

[Andy Wingo <wingo@pobox.com>]

Hi Neil,

On Mon 28 Jun 2010 23:48, Neil Jerram <neil@ossau.uklinux.net> writes:

> 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') ?

This is not a known problem to me, and the build has not changed;
however it seems you are working on an old revision. Some things changed
in the past that required a clean build. Can you try that?

Furthermore in the past the meta/uninstalled-env wasn't setting
GUILE_SYSTEM_PATH properly, so it would pick up installed .scm files.

> If I then go to a shell:
>
> neil@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.

This is fishy; nothing in current code calls scm_trampoline_1.

> 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

Indeed.

> 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

Yes, they are harmless warnings. You don't get these warnings with
automake 1.11. 

FWIW I'm going to not be around very much until sometime next week, so
apologies in advance for delayed replies :)

Regards,

Andy
-- 
http://wingolog.org/