From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-12-10
Date: Thu, 11 Dec 2014 17:58:55 +0000 [thread overview]
Message-ID: <5489DB5F.2000101@imgtec.com> (raw)
In-Reply-To: <20141211175508.GQ2440@tarshish>
Dear Baruch Siac,
On 12/11/2014 05:55 PM, Baruch Siach wrote:
> Hi Vicente,
>
> On Thu, Dec 11, 2014 at 05:39:46PM +0000, Vicente Olivert Riera wrote:
>> 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
>> cross-compiling.
>>
>> However, after doing that, we will face more problems. The first one
>> will be one related of a missing "-pthread" option:
>>
>> /br/output/host/usr/mipsel-buildroot-linux-uclibc/sysroot/usr/lib/libnl-3.a(socket.o):
>> 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:
>>
>> KISMET_CONF_ENV = LIBS="-pthread"
>>
>> But that's not enough. We will face more problems like this one:
>>
>> /br/output/host/usr/mipsel-buildroot-linux-uclibc/sysroot/usr/lib/libpcap.a(pcap-canusb-linux.o):
>> 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?
>
> Use the pcap-config utility. See for example the packages bustle and wireshark
> among the others.
oh, that's interesting. Thanks! I have to go now, but I will have a look
at it tomorrow, unless someone fix it first :P
Cheers,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-12-11 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-12-10 Thomas Petazzoni
2014-12-11 17:39 ` Vicente Olivert Riera
2014-12-11 17:55 ` Baruch Siach
2014-12-11 17:58 ` Vicente Olivert Riera [this message]
2014-12-12 10:53 ` Vicente Olivert Riera
2014-12-12 11:06 ` Thomas Petazzoni
2014-12-12 12:27 ` Vicente Olivert Riera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5489DB5F.2000101@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox