From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 4/4] package/fwupd: new package
Date: Tue, 16 Jul 2024 21:47:24 +0200 [thread overview]
Message-ID: <20240716214724.62a772d4@windsurf> (raw)
In-Reply-To: <CADvTj4pA9E8H7=S5HKBHwUhgKq8c_+TcRcu1BAMSBxPNTwTX0Q@mail.gmail.com>
Hello James,
Thanks for the quick turnaround. One question below.
On Tue, 16 Jul 2024 11:55:18 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Fixed in v3 by setting -Dudevdir=/usr/lib/udev which eliminates the
> udev dependency.
It seems very odd to me to set -Dudevdir=/usr/lib/udev when the
directory doesn't exist because udev isn't enabled. Could you clarify
how this can be correct?
> > Which probably you had not seen because you had jinja2 installed on
> > your system. Could you make sure to test build packages with
> > ./utils/docker-run to catch such "spurious" host dependencies?
>
> It was missed because I was testing with systemd enabled, which has a
> transitive dependency on host-python-jinja2.
Indeed.
> > I quickly grepped for jinja2 in the tree, but it wasn't immediately
> > clear if it was absolutely mandatory, exactly for what, etc. Hopefully
> > you'll be able to figure out. It would be nice to not make it a
> > mandatory dependency to build fwupd, if possible of course.
>
> Yeah, it's mandatory for some scripts, fixed in v3.
OK.
> v3:
> https://patchwork.ozlabs.org/project/buildroot/patch/20240716175037.1844929-5-james.hilliard1@gmail.com/
Thanks!
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:[~2024-07-16 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 15:21 [Buildroot] [PATCH v2 1/4] package/libjcat: new package James Hilliard
2024-06-11 15:22 ` [Buildroot] [PATCH v2 2/4] package/fwupd-efi: " James Hilliard
2024-06-11 15:22 ` [Buildroot] [PATCH v2 3/4] package/flashrom: install to staging with meson James Hilliard
2024-07-16 12:40 ` Thomas Petazzoni via buildroot
2024-06-11 15:22 ` [Buildroot] [PATCH v2 4/4] package/fwupd: new package James Hilliard
2024-07-16 12:17 ` Thomas Petazzoni via buildroot
2024-07-16 17:55 ` James Hilliard
2024-07-16 19:47 ` Thomas Petazzoni via buildroot [this message]
2024-07-16 19:56 ` James Hilliard
2024-07-16 22:17 ` Thomas Petazzoni via buildroot
2024-07-18 16:03 ` James Hilliard
2024-07-16 12:39 ` [Buildroot] [PATCH v2 1/4] package/libjcat: " 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=20240716214724.62a772d4@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=james.hilliard1@gmail.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