From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpdump: use libpcap shared library
Date: Thu, 30 Oct 2014 22:01:08 +0100 [thread overview]
Message-ID: <20141030220108.2258b647@free-electrons.com> (raw)
In-Reply-To: <67c0a327947d1f710687a04d56a3a047984f3988.1414585221.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Wed, 29 Oct 2014 14:20:21 +0200, Baruch Siach wrote:
> Currently the tcpdump configure script finds libpcap.a in
> output/build/libpcap-[version]. This check is hard coded in aclocal.m4. Add a
> patch to optionally ignore local libpcap so that the system shared library
> version is found instead. This reduces the tcpdump binary size in a few 100KB.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> ...libpcap-when-configured-with-with-system-.patch | 78 ++++++++++++++++++++++
> package/tcpdump/tcpdump.mk | 7 +-
> 2 files changed, 83 insertions(+), 2 deletions(-)
> create mode 100644 package/tcpdump/0001-Use-system-libpcap-when-configured-with-with-system-.patch
Applied, thanks.
However, the tcpdump library has an invalid rpath:
0x0000000f (RPATH) Library rpath: [/home/thomas/projets/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib]
This rpath comes from the fact that pcap-config returns a -Wl,-rpath
option that it should not. If you have some time to look into that, it
would be good (especially if it's done in a way acceptable upstream!).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-30 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 12:20 [Buildroot] [PATCH] tcpdump: use libpcap shared library Baruch Siach
2014-10-30 7:20 ` Baruch Siach
2014-10-30 21:01 ` Thomas Petazzoni [this message]
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=20141030220108.2258b647@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.