Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 15:26:57 +0100	[thread overview]
Message-ID: <20251210152657.5422b252@windsurf> (raw)
In-Reply-To: <20251210151337.7c42babf@kmaincent-XPS-13-7390>

Hello,

On Wed, 10 Dec 2025 15:13:37 +0100
Kory Maincent <kory.maincent@bootlin.com> wrote:

> > 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.  
> 
> Oh wow, my brain read --enable-uuid and --disable-uuid.
> uuid and libuuid are indeed two distinct things, sorry for the confusion.
>  
> > Which specific tool was missing in your case?  
> 
> I was needing the uuidgen tool on my case.
> That why I need to enable uuid.

And --enable-uuidd controls whether uuidgen is built?

I'll generally be fine with dropping --disable-uiidd, but please
provide a good commit log, explaining the difference in build time
(since it's a host package, we don't care about the difference in
installed size). I presume the build time difference will be minimal if
not negligible.

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

  reply	other threads:[~2025-12-10 14:27 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
2025-12-10 14:13   ` Kory Maincent via buildroot
2025-12-10 14:26     ` Thomas Petazzoni via buildroot [this message]
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=20251210152657.5422b252@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