From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/util-linux: Fix host uuidd build configuration
Date: Wed, 10 Dec 2025 14:57:15 +0100 [thread overview]
Message-ID: <20251210145715.50e51799@windsurf> (raw)
In-Reply-To: <20251210102940.2535550-1-kory.maincent@bootlin.com>
Hello,
On Wed, 10 Dec 2025 10:29:39 +0000
Kory Maincent <kory.maincent@bootlin.com> wrote:
> The host build had conflicting configuration options where libuuid was
> simultaneously enabled and disabled. Although comments explicitly stated
> that libuuid should be enabled for the host, the --disable-uuidd flag
> was preventing the uuid tools from being built and installed.
Sorry, but I don't really understand the conflict. --enable-libuuid to
me does not conflict with --disable-uuidd. --enable-libuuid enables the
libuuid library, --disable-uuidd disables the uuidd daemon, which can
optionally be used by libuuid, but isn't strictly needed.
Which specific tool was missing in your case?
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-12-10 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 10:29 [Buildroot] [PATCH] package/util-linux: Fix host uuidd build configuration Kory Maincent via buildroot
2025-12-10 13:57 ` Thomas Petazzoni via buildroot [this message]
2025-12-10 14:13 ` Kory Maincent via buildroot
2025-12-10 14:26 ` Thomas Petazzoni via buildroot
2025-12-10 14:38 ` Kory Maincent via buildroot
2025-12-10 14:59 ` Kory Maincent 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=20251210145715.50e51799@windsurf \
--to=buildroot@buildroot.org \
--cc=kory.maincent@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox