Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/wolfssl: disable examples and tests
Date: Thu, 3 Sep 2020 21:04:09 +0200	[thread overview]
Message-ID: <20200903210409.6384c462@windsurf.home> (raw)
In-Reply-To: <20200902204310.3909104-1-fontaine.fabrice@gmail.com>

On Wed,  2 Sep 2020 22:43:10 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Examples and tests are not needed especially because of them fails on
> some architectures because it wrongly tries to use wc_Sha256FinalRaw:
> 
>   CCLD     tests/unit.test
> /tmp/instance-0/output-1/host/opt/ext-toolchain/bin/../lib/gcc/aarch64-none-linux-gnu/9.2.1/../../../../aarch64-none-linux-gnu/bin/ld: tests/tests_unit_test-api.o: in function `test_wc_Sha256FinalRaw':
> /tmp/instance-0/output-1/build/wolfssl-4.5.0-stable/tests/api.c:6504: undefined reference to `wc_Sha256FinalRaw'
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/d5b6f97f7510874fe28c675e599be08cb8a78c7b
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/wolfssl/wolfssl.mk | 2 ++
>  1 file changed, 2 insertions(+)

Applied to master, thanks. However, this sort of commit log still lacks
one very fundamental information: since when this problem is happening.
Without this information, we have no idea if this patch needs to be
backported to our stable branches. Could you pay attention to this in
your next submission of fixes ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-09-03 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 20:43 [Buildroot] [PATCH 1/1] package/wolfssl: disable examples and tests Fabrice Fontaine
2020-09-03 19:04 ` Thomas Petazzoni [this message]
2020-09-05  8:27 ` Peter Korsgaard

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=20200903210409.6384c462@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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