From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12096] tcpreplay: build fails if libdumbnet-dev is installed in the host
Date: Tue, 13 Aug 2019 19:41:24 +0000 [thread overview]
Message-ID: <bug-12096-163-MB4rcEY7S0@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12096-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12096
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Fixed by
https://git.buildroot.org/buildroot/commit/?id=3a4b68278ab20aee6de80bc9001788c4558282d2
and
https://git.buildroot.org/buildroot/commit/?id=3cd991c226539316e0db94573780cf51261410f8
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-08-13 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 9:58 [Buildroot] [Bug 12096] New: tcpreplay: build fails if libdumbnet-dev is installed in the host bugzilla at busybox.net
2019-08-08 14:09 ` [Buildroot] [Bug 12096] " bugzilla at busybox.net
2019-08-13 19:41 ` bugzilla at busybox.net [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=bug-12096-163-MB4rcEY7S0@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 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.