From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/3] package/log4cxx: fix boost-fallback (only check for boost if really needed)
Date: Sun, 30 Jan 2022 23:40:14 +0100 [thread overview]
Message-ID: <20220130234014.3cf1a805@windsurf> (raw)
In-Reply-To: <20220128124538.31789-2-ps.report@gmx.net>
On Fri, 28 Jan 2022 13:45:37 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> - add patch 0002-boost-fallback-only-check-for-boost-if-really-needed.patch
> to check for boost if really needed (in case of legacy c++ standard < c++17)
>
> Fixes:
>
> - http://autobuild.buildroot.net/results/8d49ab7cd9952f6a13bdd330e875012d0601f1d2
>
> -- Found Boost: .../host/x86_64-buildroot-linux-uclibc/sysroot/usr/include (found version "1.78.0") found components: thread chrono missing components: date_time atomic
> CMake Error at .../build/log4cxx-0.12.0/boost-fallback-compile-tests/CMakeFiles/CMakeTmp/CMakeLists.txt:19 (add_executable):
> Target "cmTC_aac37" links to target "Boost::date_time" but the target was
> not found. Perhaps a find_package() call is missing for an IMPORTED
> target, or an ALIAS target is missing?
>
> CMake Error at .../build/log4cxx-0.12.0/boost-fallback-compile-tests/CMakeFiles/CMakeTmp/CMakeLists.txt:19 (add_executable):
> Target "cmTC_aac37" links to target "Boost::atomic" but the target was not
> found. Perhaps a find_package() call is missing for an IMPORTED target, or
> an ALIAS target is missing?
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> ...nly-check-for-boost-if-really-needed.patch | 36 +++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 package/log4cxx/0002-boost-fallback-only-check-for-boost-if-really-needed.patch
Took me a while to understand what was going on here, but I think I got it:
* If we have gcc < 7.x, then log4cxx needs boost, and makes sure boost
is built with the date-time support.
* If we have gcc >= 7.x, then log4cxx does not need boost, but the
CMake logic in src/cmake/boost-fallback/boost-fallback.cmake kicks
in anyway, and tests if date-time is provided, which fails.
So what your patch does is to only conditionally do the Boost checks in
src/cmake/boost-fallback/boost-fallback.cmake if Boost is really needed.
Looks good to me: applied!
Thanks a lot!
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-01-30 22:40 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 [this message]
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
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=20220130234014.3cf1a805@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--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