Gregory> As reported in pre1, specifying more than two database types yields an Gregory> error: Gregory> ../configure: Usage error: Gregory> The `--with-database' option value Gregory> must be either `no' or a comma-separated list Gregory> of one or more of `berkdb', `dbm', or `gnudbm'. Gregory> Use `../configure --help' to show usage. Gregory> The problem is the separation of the values only replaces the first comma Gregory> instead of all of them: Gregory> for x in `echo "$val" | sed -e 's/,/ /'` ; do Gregory> Here is a patch to fix the problem: Gregory> --- configure.in~orig Thu Jul 9 22:58:19 1998 Gregory> +++ configure.in Thu Jul 9 22:58:30 1998 Gregory> ＠＠ -570,7 +570,7 ＠＠ Gregory> with_database_berkdb=no Gregory> with_database_dbm=no Gregory> with_database_gnudbm=no Gregory> - for x in `echo "$val" | sed -e 's/,/ /'` ; do Gregory> + for x in `echo "$val" | sed -e 's/,/ /g'` ; do Gregory> case "$x" in Gregory> no ) ;; Gregory> b | be | ber | berk | berkd | berkdb ) with_database_berkdb=yes ;; I don't think this is right, since there are really only two database types, `dbm', and `berkdb'. gdbm is just another implementation of `dbm'. I think you can't have both `dbm' and `gdbm' actually in use within the same xemacs. This is even more confusing since I believe berkdb can also provide the `dbm' api. (not claiming to be a database expert, though). The patch should be applied on general principles, however, since any time a list is split into words, the possibility of more than 2 words should be taken into account. Just don't expect to be able to get dbm and gdbm after you're done. Martin

Martin> I don't think this is right, since there are really only two database Martin> types, `dbm', and `berkdb'. gdbm is just another implementation of Martin> `dbm'. I think you can't have both `dbm' and `gdbm' actually in use Martin> within the same xemacs. This is even more confusing since I believe Martin> berkdb can also provide the `dbm' api. (not claiming to be a database Martin> expert, though). Gregory> I agree that at the moment, only two selections will work but the error Gregory> given would be incorrect for the command: Gregory> * ) USAGE_ERROR(["The \`--$optname' option value Gregory> must be either \`no' or a comma-separated list Gregory> of one or more of \`berkdb', \`dbm', or \`gnudbm'."]) ;; Gregory> It doesn't say one or two, it says one or more. If three are given it Gregory> gives this error and leaves the user wondering what they did wrong. After Gregory> the patch is applied, if they user types all three, they at least get an Gregory> error which makes sense: Gregory> USAGE_ERROR("Only one of \`dbm' and \`gnudbm' may be specified Gregory> with the \`--$optname' option.") Martin> Just don't expect to be able to get dbm and gdbm after you're done. Gregory> Never did, I saw the error following that case when I first ran across Gregory> this. OK, we are in complete agreement then. Thank you. Martin