All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Scheel <julian@jusst.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/4] Add package cryptopp
Date: Fri, 22 Apr 2016 09:29:32 +0200	[thread overview]
Message-ID: <5719D2DC.9020702@jusst.de> (raw)
In-Reply-To: <20160421224000.031987c9@free-electrons.com>

Hi Thomas,

On 21.04.2016 22:40, Thomas Petazzoni wrote:
> On Thu, 17 Mar 2016 16:03:55 +0100, Julian Scheel wrote:
>> Signed-off-by: Julian Scheel <julian@jusst.de>
>> ---
>>   package/cryptopp/cryptopp.hash |  2 ++
>>   package/cryptopp/cryptopp.mk   | 33 +++++++++++++++++++++++++++++++++
>>   2 files changed, 35 insertions(+)
>>   create mode 100644 package/cryptopp/cryptopp.hash
>>   create mode 100644 package/cryptopp/cryptopp.mk
>
> This package causes some build failures:
>
>    http://autobuild.buildroot.org/?reason=host-cryptopp-5.6.3
>
> Could you have a look at them?

Should be fixed by:
[PATCH] package/cryptopp: Backport gcc compatibility patch

-Julian

  reply	other threads:[~2016-04-22  7:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 15:03 [Buildroot] [PATCHv2 0/4] Add flashing tools for tegra processors Julian Scheel
2016-03-17 15:03 ` [Buildroot] [PATCHv2 1/4] Add package cryptopp Julian Scheel
2016-04-19 20:23   ` Thomas Petazzoni
2016-04-21 20:40   ` Thomas Petazzoni
2016-04-22  7:29     ` Julian Scheel [this message]
2016-03-17 15:03 ` [Buildroot] [PATCHv2 2/4] Add package tegrarcm Julian Scheel
2016-04-19 20:24   ` Thomas Petazzoni
2016-03-17 15:03 ` [Buildroot] [PATCHv2 3/4] Add package cbootimage Julian Scheel
2016-04-19 20:34   ` Thomas Petazzoni
2016-03-17 15:03 ` [Buildroot] [PATCHv2 4/4] Add package cbootimage-configs Julian Scheel
2016-04-19 21:08   ` Thomas Petazzoni
2016-04-19 22:36     ` Arnout Vandecappelle
2016-04-20  6:18     ` Julian Scheel
2016-04-20  7:11       ` Thomas Petazzoni

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=5719D2DC.9020702@jusst.de \
    --to=julian@jusst.de \
    --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.