From: Nathaniel Roach <nroach44@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] bandwidthd: incorporate fixes for autobuilders
Date: Mon, 18 Aug 2014 22:40:58 +0800 [thread overview]
Message-ID: <53F2107A.5040008@gmail.com> (raw)
In-Reply-To: <53F20353.8020107@openwide.fr>
On 18/08/14 21:44, Romain Naour wrote:
> Hi Nathaniel,
>
> [snip]
>
> There is a new build issue with bandwidthd:
>
> http://autobuild.buildroot.net/results/37a/37a94e0f2d3faa0aec9c488e987cfff706fc9f3b/build-end.log
>
>
> checking for png_read_info in -lpng... no
> configure: error: Bandwidthd requires but cannot libpng
> make: *** [/home/test/autobuild/instance-3/output/build/bandwidthd-v2.0.1-auto-r08/.stamp_configured] Error 1
>
> I checked the dependencies with libpng, it's ok.
>
> But in config.log there are some link issue:
> /home/naourr/git/buildroot/test/bandwidthd/host/usr/x86_64-buildroot-linux-uclibc/sysroot/usr/lib/../lib64/libpng.a(pngread.o): In function `png_read_destroy':
> /home/naourr/git/buildroot/test/bandwidthd/build/libpng-1.6.12/pngread.c:942: undefined reference to `inflateEnd'
>
> The configure script doesn't check for zlib, then -lz is missing during libpng test
>
> I added this line to add this check before libpng:
> AC_CHECK_LIB(z, zlibVersion, , AC_MSG_ERROR(zlib not installed))
>
> The build continue but fail with libpcap:
>
> checking for zlibVersion in -lz... yes
> checking for png_read_info in -lpng... yes
> checking for gdImageCreate in -lgd... yes
> checking for pcap_open_live in -lpcap... no
> checking for pcap_open_live in -lwpcap... no
> configure: error: Bandwidthd requires but cannot find libpcap
>
> Again a link issue:
> /home/naourr/git/buildroot/test/bandwidthd/host/usr/x86_64-buildroot-linux-uclibc/sysroot/usr/lib/../lib64/libpcap.a(pcap-canusb-linux.o): In function `canusb_activate':
> /home/naourr/git/buildroot/test/bandwidthd/build/libpcap-1.6.1/./pcap-canusb-linux.c:344: undefined reference to `libusb_init'
>
> I borrowed the libusb test from libpcap to check for libusb-1.0
> # needed by libpcap
> AC_CHECK_HEADER(libusb-1.0/libusb.h,
> [
> AC_CHECK_LIB(usb-1.0, libusb_init,
> [
> LIBS="-lusb-1.0 -lpthread $LIBS"
> ac_lbl_has_libusb=yes
> ],
> [AC_MSG_ERROR([Bandwidthd requires but cannot find libusb])]
> ac_lbl_has_libusb=no,
> -lpthread
> )
> ],
> ac_lbl_has_libusb=no
> [AC_MSG_ERROR([Bandwidthd requires but cannot find libusb])]
> )
>
> And all build fine now :)
>
> Note that -lpthread need to be added here otherwise libusb will fail with pthread functions.
>
> So, the configure.ac script needs to be consolidated to check for zlib, libusb-1.0 and pthread.
> Currently, I don't have a clean patch to suggest.
>
> I hope this will help you.
>
> Best regards,
> Romain
>
Hi Romain
All: I replied earlier just to Romain, acknowledging the issue, and
forgot to click reply all instead of normal reply.
Romain, could you try building the latest master from
github.com/nroach44/bandwidthd (id:
0473a5f2527201d83c5b0ddc581b7c9f21fbdcaf )
Thanks, Nathaniel
next prev parent reply other threads:[~2014-08-18 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 0:27 [Buildroot] [PATCH v2] bandwidthd: incorporate fixes for autobuilders Nathaniel Roach
2014-08-15 9:06 ` Peter Korsgaard
2014-08-18 13:44 ` Romain Naour
2014-08-18 14:40 ` Nathaniel Roach [this message]
2014-08-18 15:01 ` Nathaniel Roach
2014-08-18 17:39 ` Romain Naour
2014-08-18 18:05 ` 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=53F2107A.5040008@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 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.