From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13261] When doing lldpd 1.0.4 Configuring, error encountered: "checking if system libevent works as expected... configure: error: *** unusable system libevent"
Date: Wed, 14 Oct 2020 03:17:59 +0000 [thread overview]
Message-ID: <bug-13261-163-SwlletC0V6@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13261-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13261
--- Comment #5 from eric.hu at nokia-sbell.com ---
(In reply to Fabrice Fontaine from comment #1)
1. Please refer to attachment config.log
2. Please refer to attachment defconfig
3. buildroot version 2020.02.6
When I do configure and make in lldp directory, it can pass, but seems libevent
is shipped which is difference with doing build from root directory, please
refer to attachment (lldp directory configure and make log)
checking for libevent... no
configure: using shipped libevent
=== configuring in libevent
(/repo/erhu/buildroot/output/build/lldpd-1.0.4/libevent)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-14 3:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 6:07 [Buildroot] [Bug 13261] New: When doing lldpd 1.0.4 Configuring, error encountered: "checking if system libevent works as expected... configure: error: *** unusable system libevent" bugzilla at busybox.net
2020-10-13 11:32 ` [Buildroot] [Bug 13261] " bugzilla at busybox.net
2020-10-14 3:13 ` bugzilla at busybox.net
2020-10-14 3:14 ` bugzilla at busybox.net
2020-10-14 3:14 ` bugzilla at busybox.net
2020-10-14 3:17 ` bugzilla at busybox.net [this message]
2020-10-14 11:45 ` bugzilla at busybox.net
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=bug-13261-163-SwlletC0V6@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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