Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 3/3] package/log4cxx: bump version to 0.12.1
Date: Sun, 30 Jan 2022 23:42:53 +0100	[thread overview]
Message-ID: <20220130234253.2023aa22@windsurf> (raw)
In-Reply-To: <20220128124538.31789-3-ps.report@gmx.net>

On Fri, 28 Jan 2022 13:45:38 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> - drop 0001-LOGCXX-528.patch (from upstream [1])
> - renumber remainnig patch
> 
> Changelog (for deteils see [2]):
> 
> - This is a minor bugfix release to fix issues found with 0.12.0. Notably,
>   this version fixes a bug where a multithreaded application would crash
>   when using a rolling file.
> 
>   [LOGCXX-534] - Crashed in log->forcedLog function when running with multi-thread
>   [LOGCXX-528] - log4cxx fails to build on Centos 7.6 / g++ 4.8.5 / Boost 1.53
> 
> [1] https://github.com/apache/logging-log4cxx/commit/249dd85494a430d95fd69d89f42b02fd950cda51
> [2] https://logging.apache.org/log4cxx/latest_stable/changelog.html#0.12.1
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  package/log4cxx/0001-LOGCXX-528.patch         | 189 ------------------
>  ...ly-check-for-boost-if-really-needed.patch} |   0
>  package/log4cxx/log4cxx.hash                  |   4 +-
>  package/log4cxx/log4cxx.mk                    |   2 +-
>  4 files changed, 3 insertions(+), 192 deletions(-)
>  delete mode 100644 package/log4cxx/0001-LOGCXX-528.patch
>  rename package/log4cxx/{0002-boost-fallback-only-check-for-boost-if-really-needed.patch => 0001-boost-fallback-only-check-for-boost-if-really-needed.patch} (100%)

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

  reply	other threads:[~2022-01-30 22:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 12:45 [Buildroot] [PATCH v1 1/3] package/log4cxx: change download URL to https Peter Seiderer
2022-01-28 12:45 ` [Buildroot] [PATCH v1 2/3] package/log4cxx: fix boost-fallback (only check for boost if really needed) Peter Seiderer
2022-01-28 13:40   ` Peter Seiderer
2022-01-30 22:40   ` Thomas Petazzoni via buildroot
2022-02-06 15:34   ` Peter Korsgaard
2022-01-28 12:45 ` [Buildroot] [PATCH v1 3/3] package/log4cxx: bump version to 0.12.1 Peter Seiderer
2022-01-30 22:42   ` Thomas Petazzoni via buildroot [this message]
2022-02-06 15:34   ` Peter Korsgaard
2022-01-30 22:19 ` [Buildroot] [PATCH v1 1/3] package/log4cxx: change download URL to https Thomas Petazzoni via buildroot
2022-02-06 15:31 ` 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=20220130234253.2023aa22@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox