All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/xerces: fix build with recent versions of ICU
Date: Sat, 3 Jan 2026 15:37:36 +0100	[thread overview]
Message-ID: <20260103153736.5f32717b@windsurf> (raw)
In-Reply-To: <20260102172639.1908616-1-bernd@kuhls.net>

Hello Bernd,

On Fri,  2 Jan 2026 18:26:39 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:

> Since Buildroot commit dcee99507c6767230fd1faeeefe95f5662eb03a3 that
> bumped package/icu to version 77-1, the build of xerces with ICU
> support enabled fails:
> 
> In file included from /home/bernd/buildroot/output/host/i586-buildroot-linux-gnu/sysroot/usr/include/unicode/uset.h:38,
>                  from /home/bernd/buildroot/output/build/xerces-3.3.0/src/xercesc/util/regx/RangeToken.cpp:40:
> /home/bernd/buildroot/output/host/i586-buildroot-linux-gnu/sysroot/usr/include/unicode/char16ptr.h:271:55:
>  error: 'is_same_v' is not a member of 'std'; did you mean 'is_same'?
> 
> Indeed, ICU now requires C++17. Instead of using a patch from Gentoo[1]
> we use a backported upstream commit, limited to CMakeLists.txt, to raise
> the c++ version.
> 
> The build error was not recorded yet by the autobuilders but can be
> reproduced with this defconfig:
> 
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_XERCES=y
> BR2_PACKAGE_ICU=y
> 
> [1] https://bugs.gentoo.org/931105
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Thanks for the patch!

Does this mean that xerces now needs some
BR2_TOOLCHAIN_GCC_AT_LEAST_xyz dependency to make sure we have a C++
compiler that supports C++17 ?

Or maybe ICU needs this? Right now it only depends on gcc >= 4.9, with
a comment saying "C++11". Is gcc 4.9 really sufficient?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-01-03 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 17:26 [Buildroot] [PATCH 1/1] package/xerces: fix build with recent versions of ICU Bernd Kuhls
2026-01-03 14:37 ` Thomas Petazzoni via buildroot [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=20260103153736.5f32717b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.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 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.