From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/util-linux: fix nommu build
Date: Fri, 16 Jan 2026 22:35:49 +0100 [thread overview]
Message-ID: <aWquaFbHJI9o1iqw@windsurf> (raw)
In-Reply-To: <20251220170623.155785-2-bernd@kuhls.net>
On Sat, Dec 20, 2025 at 06:06:21PM +0100, Bernd Kuhls wrote:
> libuuid/src/gen_uuid.c: In function 'uuid_generate_time_generic':
> libuuid/src/gen_uuid.c:629:17: error: implicit declaration of function 'pthread_atfork';
> did you mean 'pthread_join'? [-Wimplicit-function-declaration]
> 629 | pthread_atfork(NULL, NULL, reset_uuidd_cache);
Since when is this happening?
> +# pthread support uses pthread_atfork, which is not available on nommu
> +ifneq ($(BR2_USE_MMU),y)
> +UTIL_LINUX_CONF_ENV += ac_cv_lib_pthread_pthread_atfork=no
> +endif
This is also the wrong fix, it should be fixed in an upstream
compatible way. The failure doesn't make sense to me. Indeed, the
configure.ac contains:
AC_CHECK_LIB([pthread], [pthread_atfork], [
PTHREAD_LIBS="-lpthread"
AC_DEFINE([HAVE_LIBPTHREAD], [1], [Define if libpthred exist])
])
So HAVE_LIBPTHREAD should only be defined if pthread_atfork() is found
in libpthread.
And the only pthread_atfork() call is within an #ifdef HAVE_LIBPTHREAD
condition:
#ifdef HAVE_LIBPTHREAD
static volatile sig_atomic_t atfork_registered;
time_t now;
if (!atfork_registered) {
pthread_atfork(NULL, NULL, reset_uuidd_cache);
atfork_registered = 1;
}
So, some investigation is needed to understand why this configure.ac +
conditional compilation logic doesn't work as it should.
But isn't this something Julien already had a look at a long time ago?
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:[~2026-01-16 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 17:06 [Buildroot] [PATCH 1/4] package/util-linux: Remove -lpthread from uuid.pc for non-threaded builds Bernd Kuhls
2025-12-20 17:06 ` [Buildroot] [PATCH 2/4] package/util-linux: fix nommu build Bernd Kuhls
2025-12-30 16:20 ` Giulio Benetti
2026-01-16 21:35 ` Thomas Petazzoni via buildroot [this message]
2025-12-20 17:06 ` [Buildroot] [PATCH 3/4] package/util-linux: add dependency to BR2_USE_MMU when needed Bernd Kuhls
2025-12-30 16:21 ` Giulio Benetti
2026-01-16 21:58 ` Thomas Petazzoni via buildroot
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2025-12-20 17:06 ` [Buildroot] [PATCH 4/4] package/util-linux: bump version to 2.41.3 Bernd Kuhls
2025-12-30 16:32 ` Giulio Benetti
2026-01-16 21:58 ` Thomas Petazzoni via buildroot
2025-12-30 16:19 ` [Buildroot] [PATCH 1/4] package/util-linux: Remove -lpthread from uuid.pc for non-threaded builds Giulio Benetti
2026-01-16 21:32 ` 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=aWquaFbHJI9o1iqw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox