Logged In: YES 
user_id=33168

Don't worry, autoconf always wins the first battle.  You
just gotta be more persistant than it. :-)

Seriously, autoconf can be a bitch.  The real trick is to
find out what about bluetooth is broken and build a little C
program that should work but doesn't.  That will be the key
to autoconf.

Here's a possible example that could get you going:

AC_MSG_CHECKING(for resizeterm)
AC_TRY_COMPILE([#include <curses.h>], void *x=resizeterm,
  AC_DEFINE(HAVE_CURSES_RESIZETERM, 1, Define if you have
the 'resizeterm' function.)
  AC_MSG_RESULT(yes),
  AC_MSG_RESULT(no)
)

That's taken from the current configure.in.  You would need
to adjust the names and the code as appropriate.

You will probably want to look at the resulting configure. 
That can help you find the names of vars.  For example, if
bluetooth is defined or not is something like
ac_cv_has_bluetooth_h and ac_cv_has_sys_bluetooth_h.  You
can find the actual values in configure.

Hope that's enough to get you going.  If not, feel free to
mail me about what you are trying and all the other details
and we can try to get this working.