end up in the dist tarfile.
(libguile_srfi_srfi_4_v_@LIBGUILE_SRFI_SRFI_4_MAJOR@_la_SOURCES):
remove srfi-4.x.
(nodist_libguile_srfi_srfi_4_v_@LIBGUILE_SRFI_SRFI_4_MAJOR@_la_SOURCES): add srfi-4.x.
(libguile_srfi_srfi_13_14_v_@LIBGUILE_SRFI_SRFI_13_14_MAJOR@_la_SOURCES): remove srfi-13.x srfi-14.x.
(nodist_libguile_srfi_srfi_13_14_v_@LIBGUILE_SRFI_SRFI_13_14_MAJOR@_la_SOURCES): add srfi-13.x srfi-14.x.
and ltdl.c in "$(srcdir)".
* evalext.c, evalext.h (s_scm_self_evaluating_p): Needed by
syntax-case macro fix.
* Makefile.am (c-tokenize.c): Look for it in $(srcdir).
* syncase.scm, psyntax.ss, psyntax.pp: Imported fixes from trunk.
* boot-9.scm (use-syntax): Return *unspecified*.
(libpath.h): use GUILE_EFFECTIVE_VERSION to compute
SCM_LIBRARY_DIR.
(version.h): generate this here rather than configure.in. This
approach tracks source edits better (i.e. more immediately).
Might be worth considering for other .in files too.
(AC_CONFIG_FILES): separate out the files that need to be chmodded
at the end of config.status. Our "default" approach using
AC_CONFIG_COMMANDS quit working (and would have needed to be
changed to AC_CONFIG_COMMANDS(,,CMDS) rather than our previous
AC_CONFIG_COMMANDS(default,CMDS), but I the new approach, using
per-file AC_CONFIG_FILES calls appears to be more "correct" in the
current autoconf docs.
it off.
* configure.in: rearrange things so that --enable-error-on-warning
uses GUILE_ERROR_ON_WARNING as an indicator and actually set the
value of CFLAGS to include -Werror at the end of configure.in so
it doesn't break any of the non-Werror clean configure tests.
Add check for assert.h since it's used in config.h.in.
uses GUILE_ERROR_ON_WARNING as an indicator and actually set the
value of CFLAGS to include -Werror at the end of configure.in so
it doesn't break any of the non-Werror clean configure tests.
Add check for assert.h since it's used in config.h.in.
