From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/libopenssl: fix BR2_OPTIMIZE_FAST build
Date: Wed, 20 Jul 2022 13:51:52 +0200 [thread overview]
Message-ID: <20220720135152.0b3508cf@windsurf> (raw)
In-Reply-To: <20220707054948.479212-1-fontaine.fabrice@gmail.com>
On Thu, 7 Jul 2022 07:49:48 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Drop unneeded SED hacks (including build_tests) to fix the following
> build failure with BR2_OPTIMIZE_FAST:
>
> In file included from crypto/async/arch/../async_local.h:30,
> from crypto/async/arch/async_null.c:11:
> crypto/async/arch/../arch/async_posix.h:32:5: error: unknown type name 'ucontext_t'
> 32 | ucontext_t fibre;
> | ^~~~~~~~~~
>
> While at it, also "drop parentheses as all it does is spawn a useless
> sub-shell" as noticed by Yann E. Morin
>
> Fixes:
> - http://autobuild.buildroot.org/results/3ce202f11a821940ff55eafa1dc7cea54b8c0da2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2 (after review of Yann E. Morin):
> - Drop SED hacks and useless parentheses
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-20 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 5:49 [Buildroot] [PATCH v2, 1/1] package/libopenssl: fix BR2_OPTIMIZE_FAST build Fabrice Fontaine
2022-07-20 11:51 ` Thomas Petazzoni via buildroot [this message]
2022-08-11 11:42 ` 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=20220720135152.0b3508cf@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=matthew.weber@collins.com \
--cc=thomas.petazzoni@bootlin.com \
/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.