From: Nathaniel Roach <nroach44@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/bandwidthd: improve configure check for zlib and libusb.
Date: Tue, 19 Aug 2014 21:28:59 +0800 [thread overview]
Message-ID: <53F3511B.70104@gmail.com> (raw)
In-Reply-To: <1408394513-5177-1-git-send-email-romain.naour@openwide.fr>
On 19/08/14 04:41, Romain Naour wrote:> The configure script doesn't
check for zlib, then -lz is missing during libpng
> test.
> The first patch add this check.
>
> If the libpcap is linked with libusb, then the libpcap check fail because
> -lusb-1.0 is missing.
> Also -lpthread need to be added since libusb depends on threads support.
> The second patch add -lusb-1.0 and -lpthread only if libusb is present.
>
> Tested with and without libusb support.
>
> Fixes:
>
http://autobuild.buildroot.net/results/37a/37a94e0f2d3faa0aec9c488e987cfff706fc9f3b/build-end.log
>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> Cc: Nathaniel Roach <nroach44@gmail.com>
--- snip ---
> +
>
Thanks Romain, your help has been instrumental in getting this stuff
fixed. Because I maintain the fork that buildroot uses in addition to
the buildroot package, I can put these fixes in upstream without adding
complexity to buildroot.
Could you do one last test using v2.0.1-auto-r09 as the version?
Hopefully this solves the dependency issues and it removes the need for
--without-x.
Thanks, Nathaniel.
next prev parent reply other threads:[~2014-08-19 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 20:41 [Buildroot] [PATCH 1/1] package/bandwidthd: improve configure check for zlib and libusb Romain Naour
2014-08-19 13:28 ` Nathaniel Roach [this message]
2014-08-19 15:59 ` Romain Naour
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=53F3511B.70104@gmail.com \
--to=nroach44@gmail.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