From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9671] stunnel build error
Date: Sun, 26 Feb 2017 14:14:47 +0000 [thread overview]
Message-ID: <bug-9671-163-PREknU6mue@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9671-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9671
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for the bug report. This has already been fixed in commit
https://git.buildroot.org/buildroot/commit/package/stunnel?id=b575baeb1ad787dac1ce31343adfd6ee3415ca41,
which will be part of the upcoming 2017.02 release.
In the mean time, you can cherry-pick this commit in your tree.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-02-26 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 13:51 [Buildroot] [Bug 9671] New: stunnel build error bugzilla at busybox.net
2017-02-26 14:14 ` bugzilla at busybox.net [this message]
2017-02-26 21:05 ` [Buildroot] [Bug 9671] " 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-9671-163-PREknU6mue@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.