[Buildroot] [autobuild.buildroot.net] Build results for 2014-12-10

Vicente Olivert Riera Vincent.Riera at imgtec.com
Thu Dec 11 17:39:46 UTC 2014

On 12/11/2014 07:30 AM, Thomas Petazzoni wrote:
>       mipsel |             kismet-2013-03-R1b | NOK | http://autobuild.buildroot.net/results/965a3e345dc0a432043b72581bff7d33561fbe0c/

This failure is caused because in the configure script Kismet tries to
do a compile test to check for pcap_open_live(). This works for shared
builds because is very common the host machine has installed the shared
library of libpcap. But when building for static, is very unlikely
having the static library of libpcap installed on the host, so that
compilation test (which runs in the host machine) fails.

Given that kismet depends on libpcap, we can ensure that the pcap
library installed on the target will be fine, so we can workaround this
error by removing the compile tests (there are three of them) from the
configure script. And that would be a patch to fix Kismet when

However, after doing that, we will face more problems. The first one
will be one related of a missing "-pthread" option:

In function `release_local_port':
socket.c:(.text+0x120): undefined reference to `pthread_rwlock_wrlock'

We could fix that just by adding this to the kismet.mk file:


But that's not enough. We will face more problems like this one:

In function `canusb_close':
pcap-canusb-linux.c:(.text+0xec): undefined reference to `libusb_close'

So, at this point I don't know if it would be better to just disable
kismet for static builds. What do you think?

Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814

More information about the buildroot mailing list