From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bandwidthd: fix static build
Date: Sun, 5 Oct 2014 15:12:02 +0200 [thread overview]
Message-ID: <20141005151202.7c149f6c@free-electrons.com> (raw)
In-Reply-To: <54314137.7020007@gmail.com>
Dear Nathaniel Roach,
On Sun, 05 Oct 2014 21:01:43 +0800, Nathaniel Roach wrote:
> Yeah, I'm starting to lean that way too. Although I was a little
> hesitant adding another build dependency, I now realise that it's
> probably getting built anyway, and the version that's currently up on
> github was more a case of "getting it to work".
pkg-config is already needed by a *lot* of packages. And it's very
quick to build (simple C code with no dependencies).
> I've had a look at pcap-config and it doesn't seem to do -lpthreads (or
> from what I could see anything useful in this case), so I'll likely
> adapt Baruch's original patch into upstream for both lpcap and lpng.
>
> It might take me a few days as my study load has increased, but I'll get
> it done.
Cool, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-05 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 6:49 [Buildroot] [PATCH] bandwidthd: fix static build Baruch Siach
[not found] ` <542CFECE.9020103@gmail.com>
2014-10-02 7:52 ` Baruch Siach
2014-10-02 7:56 ` Nathaniel Roach
2014-10-02 7:58 ` Baruch Siach
2014-10-02 8:24 ` Nathaniel Roach
2014-10-02 8:33 ` Baruch Siach
2014-10-03 6:35 ` Nathaniel Roach
2014-10-05 4:50 ` Baruch Siach
2014-10-05 12:40 ` Thomas Petazzoni
2014-10-05 13:01 ` Nathaniel Roach
2014-10-05 13:12 ` 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=20141005151202.7c149f6c@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.