title: hcidump binary not found
body: <p>I'm setting up the BlueZ protocol stack on a custom system using linux 3.3. I'm using buildroot to setup the filesystem, and specifically am using BlueZ-4.101.</p>
  
  <p>I'm attempting to use the <code>hcidump</code> utility to get some logs, but the binary has not been installed.</p>
  
  <p>I've checked that:</p>
  
  <ul>
  <li>Device driver is installed in kernel</li>
  <li>BlueZ Utils is enabled in buildroot .config file</li>
  <li>Other utilities work, such as <code>hcitool</code> or <code>hciconfig</code> </li>
  </ul>
  
  <p>Going into the <code>Makefile</code> in <code>output/build/bluez_utils-4.101</code> it would appear that the object file <code>hcidump.o</code> is being compiled into a binary called <code>btmon</code>.</p>
  
  <p>Further investigation would reveal that in <code>Makefile</code>, <code>btmon</code>is assigned to <code>am__EXEEXT_10</code>, and that is then assigned to the variable <code>noinst_PROGRAMS</code>.</p>
  
  <p>So this is where I'm at. I'm pretty sure that this is an automatically generated <code>Makefile</code> by buildroot. I'm not sure how these files are generated, thus I'm unsure as to why <code>btmon</code> is being assigned to the <code>noinst_PROGRAMS</code> variable.</p>
  
  <p>In summary, I believe that my version of BlueZ uses a binary <code>btmon</code> instead of <code>hcidump</code>. <code>btmon</code> is compiled (binary seen at <code>output/build/bluez_utils-4.101/monitor/btmon</code>), but not being installed onto my target system because of instructions in <code>Makefile</code>.</p>
  
  <p>My best guess would something weird about compatibility between my kernel version and bluez. Any suggestions would be greatly appreciated!</p>