Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9321] Vanilla libcrypt++ v5.6.3 doesn't allow to work Nvidia Tegra's flash utility (tegrarcm)
Date: Sat, 22 Oct 2016 20:36:05 +0000	[thread overview]
Message-ID: <bug-9321-163-5Rvg9tKY51@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9321-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9321

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 for your patch. However, all your patches (except the conversion to
autotools) have already been merged in upstream cryptopp, so I've simply bumped
our cryptopp package to version 5.6.5.

See
https://git.buildroot.org/buildroot/commit/?id=da90437be784fa88e1f149067056096dd6847c26
for more details.

Do not hesitate to test tegrarcm again with this updated cryptopp version, and
report back. Thanks a lot!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2016-10-22 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 15:42 [Buildroot] [Bug 9321] New: Vanilla libcrypt++ v5.6.3 doesn't allow to work Nvidia Tegra's flash utility (tegrarcm) bugzilla at busybox.net
2016-09-29 15:44 ` [Buildroot] [Bug 9321] " bugzilla at busybox.net
2016-10-22 20:36 ` 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-9321-163-5Rvg9tKY51@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