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/RFC 2/3] package/taglib: needs gcc >= 7
Date: Mon, 24 Aug 2026 22:01:21 +0200	[thread overview]
Message-ID: <aoyi1476LyooLpig@windsurf> (raw)
In-Reply-To: <20260724164829.304335-2-bernd@kuhls.net>

On Fri, Jul 24, 2026 at 06:48:28PM +0200, Bernd Kuhls wrote:
> Fixes a build error caught by the Gitlab pipelines:
> 
> /builds/bkuhls/buildroot/br-test-pkg/bootlin-aarch64-glibc-old/build/taglib-2.3/taglib/mpeg/mpegfile.cpp:113:10:
>  error: expected primary-expression before ‘const’
>        if(const Header header(&file, headerOffset + i, true); header.isValid()) {
> 
> which was introduced by code format changes in upstream commit
> https://github.com/taglib/taglib/commit/dfe2aa52532fc9f73a67499dd17fb527a856a22f
> 
> which was first released with taglib 2.0, added to buildroot with commit
> 9cd3464afa13fd0190fb3e94fd850cc8063cf297.
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> I have no idea if this patch is correct, at least blocking gcc 6 makes
> the Gitlab pipelines happy. It seems to me that the upstream commit uses
> newer language features not supported by gcc 6, but with my limited
> knowledge about C++ I could not find evidence to support my theory.

I'm also not a C++ guru, but some research shows that this is called
"init-statement", was described by proposal P0305R1 and according to
https://en.cppreference.com/cpp/compiler_support/17 this feature
indeed has been supported since gcc 7.

I've extended the commit log with this information, and applied to
master. Thanks!

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-08-24 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 16:48 [Buildroot] [PATCH 1/3] package/taglib: mp4 support needs threads Bernd Kuhls
2026-07-24 16:48 ` [Buildroot] [PATCH/RFC 2/3] package/taglib: needs gcc >= 7 Bernd Kuhls
2026-08-24 20:01   ` Thomas Petazzoni via buildroot [this message]
2026-09-04 12:18   ` Thomas Perale via buildroot
2026-07-24 16:48 ` [Buildroot] [PATCH 3/3] package/taglib: bump version to 2.3.1 Bernd Kuhls
2026-08-24 20:10   ` Thomas Petazzoni via buildroot
2026-08-24 20:00 ` [Buildroot] [PATCH 1/3] package/taglib: mp4 support needs threads Thomas Petazzoni via buildroot

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=aoyi1476LyooLpig@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.