Revision 58921

Fix a problem with BDB detection. There were conflicts across the
functions because of the variable names. Unfortunately, we don't have
actual scoping on these variables :-)

In the particular case that I saw, APU_CHECK_DB41() would set the $places
variable because it was unset. However, the APU_CHECK_ALL() would then
pass that *modified* $places value into APU_CHECK_DB4(). Thus, my BDB 4.0
check was looking in /usr/local/BerkeleyDB.4.1, even though I hadn't told
it to look anywhere (iow, wrong defaults for BDB 4.0).

The fix is simply to use different variable names for the "higher-level"
functions which call into the lower-level functions. The low-level funcs
can reuse the variable no problem since they initialize it from the
(empty) parameter which is passed to them.