From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad@gadz.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/graphene: needs a toolchain with threads
Date: Mon, 12 Aug 2024 22:03:41 +0200 [thread overview]
Message-ID: <20240812220341.02fc74ae@windsurf> (raw)
In-Reply-To: <20240811080755.2588426-1-francois.perrad@gadz.org>
Hello François,
On Sun, 11 Aug 2024 10:07:55 +0200
Francois Perrad <francois.perrad@gadz.org> wrote:
> /home/autobuild/autobuild/instance-9/output-1/host/aarch64-buildroot-linux-uclibc/sysroot/usr/include/features.h:220:5: warning: #warning requested reentrant code, but thread support was disabled [-Wcpp]
>
> fix http://autobuild.buildroot.org/results/9b3/9b357b1ef2eccd3110d0ecaaff1ae4883dff9280
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/graphene/Config.in | 4 ++++
> 1 file changed, 4 insertions(+)
Thanks a lot, but I believe this is papering over the real issue.
Indeed the code has some nice:
#ifdef HAVE_PTHREAD
...
#endif
around all thread related code. However, the:
threadlib = dependency("threads")
in meson.build adds -pthread to the build command line, causing this
issue. I am not an expert in Meson so I'm not 100% sure how to fix
this, and to understand 100% what is the semantic of
dependency("threads"), but this is what needs to be fixed (or
alternatively reported upstream). Maybe meson.build needs to be changed this way:
test if pthread.h is here, and if it is:
set HAVE_PHTHREAD
threadlib = dependency("threads")
something along those lines. Could you have a look?
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
prev parent reply other threads:[~2024-08-12 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 8:07 [Buildroot] [PATCH] package/graphene: needs a toolchain with threads Francois Perrad
2024-08-12 20:03 ` 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=20240812220341.02fc74ae@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=francois.perrad@gadz.org \
--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.