From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9506] Collectd 5.7.0 fails to build with libcrypt
Date: Sun, 26 Feb 2017 20:23:37 +0000 [thread overview]
Message-ID: <bug-9506-163-4lA32yp5Pz@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9506-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9506
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks Roland for your bug report. This issue has been fixed in January by
commit
https://git.buildroot.org/buildroot/commit/package/collectd?id=01cd62a31c2e04ea9acaca9cfca527a938e40e85.
Do not hesitate to let us know if you think the issue is still unresolved for
you.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-02-26 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 12:22 [Buildroot] [Bug 9506] New: Collectd 5.7.0 fails to build with libcrypt bugzilla at busybox.net
2017-02-26 20:23 ` 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-9506-163-4lA32yp5Pz@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.