All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9321] New: Vanilla libcrypt++ v5.6.3 doesn't allow to work Nvidia Tegra's flash utility (tegrarcm)
Date: Thu, 29 Sep 2016 15:42:33 +0000	[thread overview]
Message-ID: <bug-9321-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9321
           Summary: Vanilla libcrypt++ v5.6.3 doesn't allow to work Nvidia
                    Tegra's flash utility (tegrarcm)
           Product: buildroot
           Version: 2016.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: andrey.volkov at nexvision.fr
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 6736
  --> https://bugs.busybox.net/attachment.cgi?id=6736&action=edit
Patch to fix this issue

Nvidia Tegra's flash utility 'tegrarcm' from the package 'tegrarcm', demands
fixed libcrypt++ library, or it will failed at wrong assert check. Patches who
fix this (and also others) issue currently presented in the debian libcrypt++
package. So I've imported and converted them to be buildroot friendly. Integral
patch attached.

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

             reply	other threads:[~2016-09-29 15:42 UTC|newest]

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