From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/libtracefs: fix build failure due to missing NPTL
Date: Fri, 15 Aug 2025 12:24:06 +0200 [thread overview]
Message-ID: <20250815122406.3d466418@windsurf> (raw)
In-Reply-To: <20250814210758.563308-1-giulio.benetti@benettiengineering.com>
Hello Giulio,
On Thu, 14 Aug 2025 23:07:58 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> At the moment package libtracefs builds utest that requires
> pthread_barrier_(), so since we don't need utest let's disable it.
>
> Fixes:
> https://autobuild.buildroot.net/results/69b/69b75908bebdf9382a4cd9b138fcaf1e34daba09//
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Thanks for the fix! Since when is this problem happening? Remember, we
need to know whether this needs to be backported to our stable 2025.02
LTS branch.
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
next prev parent reply other threads:[~2025-08-15 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 21:07 [Buildroot] [PATCH] package/libtracefs: fix build failure due to missing NPTL Giulio Benetti
2025-08-15 10:24 ` Thomas Petazzoni via buildroot [this message]
2025-08-15 11:09 ` [Buildroot] [PATCH v2] " Giulio Benetti
2025-08-15 15:19 ` Thomas Petazzoni via buildroot
2025-08-15 16:41 ` Giulio Benetti
2025-08-15 18:32 ` Thomas Petazzoni via buildroot
2025-08-15 20:35 ` [Buildroot] [PATCH v3] " Giulio Benetti
2025-08-16 20:05 ` Thomas Petazzoni via buildroot
2025-08-21 19:21 ` [Buildroot] [PATCH] " Thomas Perale 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=20250815122406.3d466418@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=maxime.chevallier@bootlin.com \
--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.