From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mongrel2: bump to version 1.12.2
Date: Thu, 15 Oct 2020 23:43:24 +0200 [thread overview]
Message-ID: <20201015234324.40152794@windsurf> (raw)
In-Reply-To: <20200907214155.842865-1-fontaine.fabrice@gmail.com>
On Mon, 7 Sep 2020 23:41:55 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Refresh second patch
> - Drop third patch (already in version)
> - An external mbedtls can be used since version 1.12.0 and
> https://github.com/mongrel2/mongrel2/commit/5be7fc9c90fd5c8caa233770b7e2cdff67b4bae2
> so use it with an upstream patch and drop
> MONGREL2_POST_CONFIGURE_HOOKS
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...-Fix-Makefiles-for-cross-compilation.patch | 41 ++++---
> ...03-Rename-symbol-to-prevent-conflict.patch | 45 -------
> ...tion-error-when-building-with-gcc10.patch} | 0
> .../0004-Support-urandom-inside-chroot.patch | 113 ++++++++++++++++++
> package/mongrel2/Config.in | 1 +
> package/mongrel2/mongrel2.hash | 5 +-
> package/mongrel2/mongrel2.mk | 21 +---
> 7 files changed, 143 insertions(+), 83 deletions(-)
> delete mode 100644 package/mongrel2/0003-Rename-symbol-to-prevent-conflict.patch
> rename package/mongrel2/{0004-fix-multiple-definition-error-when-building-with-gcc10.patch => 0003-fix-multiple-definition-error-when-building-with-gcc10.patch} (100%)
> create mode 100644 package/mongrel2/0004-Support-urandom-inside-chroot.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-10-15 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 21:41 [Buildroot] [PATCH 1/1] package/mongrel2: bump to version 1.12.2 Fabrice Fontaine
2020-09-08 6:50 ` Lionel Orry
2020-09-08 11:28 ` Fabrice Fontaine
2020-09-08 11:36 ` Lionel Orry
2020-10-15 21:43 ` Thomas Petazzoni [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=20201015234324.40152794@windsurf \
--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