From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org, Pierre-Jean Texier <texier.pj2@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/haveged: needs threads
Date: Sat, 10 Oct 2026 17:24:32 +0200 [thread overview]
Message-ID: <aspYrBQMJbnHyhR9@windsurf> (raw)
In-Reply-To: <20260925060237.2488685-1-yegorslists@googlemail.com>
On Fri, Sep 25, 2026 at 08:02:37AM +0200, Yegor Yefremov via buildroot wrote:
> Since the bump to version 1.9.15 in commit
> 2a28d25d0c61 ("package/haveged: bump to version 1.9.15"), haveged
> unconditionally includes <semaphore.h> and uses named semaphores
> (sem_open() and friends) to synchronize command instances. As a
> result, the build fails with toolchains without threads support:
>
> haveged.c:37:10: fatal error: semaphore.h: No such file or directory
>
> Add a dependency on BR2_TOOLCHAIN_HAS_THREADS. Since threads are now
> always available, unconditionally pass --enable-threads.
>
> Fixes:
> https://autobuild.buildroot.org/results/814cb7b5537d8b7b2c23f3d90e37b2b41de7ee3f
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Assisted-by: Claude:claude-opus-5-5
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
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:[~2026-10-10 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 6:02 [Buildroot] [PATCH] package/haveged: needs threads Yegor Yefremov via buildroot
2026-10-10 15:24 ` 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=aspYrBQMJbnHyhR9@windsurf \
--to=buildroot@buildroot.org \
--cc=texier.pj2@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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