Hi! I first tried it on the openssh ml, but they told me it'd rather look like a bug in autoconf, so here I am.
This is my problem: If I leave the openssh 3.1p1 sources untouched, it works fine with paths containing a comma (,). But after just running autoconf (without touching anything else), configure chokes on these paths: === Begin screenshot === configure: creating ./config.status config.status: creating Makefile sed: -e expression #1, char 435: Unknown option to 's' config.status: creating openbsd-compat/Makefile sed: -e expression #1, char 480: Unknown option to 's' config.status: creating scard/Makefile sed: -e expression #1, char 453: Unknown option to 's' config.status: creating ssh_prng_cmds sed: -e expression #1, char 445: Unknown option to 's' config.status: creating config.h === End screenshot === That's because the paths are used unquoted in config.status: === Begin extract from config.status === sed " :t /@[a-zA-Z_][a-zA-Z_0-9]*@/!b s,@configure_input@,$configure_input,;t t s,@srcdir@,$ac_srcdir,;t t s,@abs_srcdir@,$ac_abs_srcdir,;t t s,@top_srcdir@,$ac_top_srcdir,;t t s,@abs_top_srcdir@,$ac_abs_top_srcdir,;t t s,@builddir@,$ac_builddir,;t t s,@abs_builddir@,$ac_abs_builddir,;t t s,@top_builddir@,$ac_top_builddir,;t t s,@abs_top_builddir@,$ac_abs_top_builddir,;t t s,@INSTALL@,$ac_INSTALL,;t t " $ac_file_inputs | (eval "$ac_sed_cmds") >$tmp/out === End extract from config.status === Any ideas how to fix this? I need to patch configure.ac to link openssh statically (urgently needed because the openssl team keeps breaking binary compatibility even on patch level releases). CU/Lnx Sascha Registered Linux User #77587 (http://counter.li.org/)
msg07324/pgp00000.pgp
Description: PGP signature
