From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/cairo: mutex support depends on NPTL
Date: Thu, 27 Jul 2023 10:56:01 +0200 [thread overview]
Message-ID: <20230727105601.577d3213@windsurf> (raw)
In-Reply-To: <20230727065417.347083-1-bernd@kuhls.net>
On Thu, 27 Jul 2023 08:54:17 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/041/041ac8f0809a0f9415c545b7585cd197db08b55f/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> The last bump of cairo took place in 2019 with commit
> 8d2a9d089a969909ad2de8acb67ee14ced03de28, the first build error of this
> kind I could find dates back to Sep 2022:
> http://autobuild.buildroot.net/results/8c5/8c547ec2e148ce3c4f230bb4b0d5c5b360d74dd5/
This could have gone in the commit message itself. I believe (but I'm
not 100% sure) that this issue started occurring when fully random
configurations started being tested. Indeed before that we were not
testing configurations with threads enabled but not NPTL, I believe.
Anyway, the fact that the issue existed in September 2022 means we need
to backport this fix to our stable 2023.02.x and 2023.05.x branches,
which is really the information that we need to have.
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
prev parent reply other threads:[~2023-07-27 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 6:54 [Buildroot] [PATCH 1/1] package/cairo: mutex support depends on NPTL Bernd Kuhls
2023-07-27 8:56 ` 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=20230727105601.577d3213@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fontaine.fabrice@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox