From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/meson: bump to version 0.61.0
Date: Wed, 12 Jan 2022 09:10:58 +0100 [thread overview]
Message-ID: <20220112091058.76318df8@windsurf> (raw)
In-Reply-To: <20220110211323.1828141-1-james.hilliard1@gmail.com>
Hello James,
On Mon, 10 Jan 2022 14:13:23 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/meson/meson.hash | 4 ++--
> package/meson/meson.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
I am wondering if this update hasn't broken some meson packages:
* polkit
http://autobuild.buildroot.net/results/b2d/b2d2b27844b32b3609e11005966d85dc0dfb7a9f/build-end.log
../output-1/build/polkit-0.120/actions/meson.build:3:5: ERROR: Function does not take positional arguments.
* host-gobject-introspection
http://autobuild.buildroot.net/results/95e/95e4a23c16f6bd96566dc497663f38a0858c5a6e/build-end.log
../output-1/build/host-gobject-introspection-1.68.0/giscanner/meson.build:51:0: ERROR: File doctemplates does not exist.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-12 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 21:13 [Buildroot] [PATCH 1/1] package/meson: bump to version 0.61.0 James Hilliard
2022-01-11 21:21 ` Thomas Petazzoni
2022-01-12 8:10 ` Thomas Petazzoni [this message]
2022-01-12 9:11 ` James Hilliard
2022-01-12 9:48 ` James Hilliard
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=20220112091058.76318df8@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=james.hilliard1@gmail.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