From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Gregor Jasny <gjasny@googlemail.com>, linux-media@vger.kernel.org
Subject: Re: [v4l-utils] [PATCH v10 1/5] Add support for meson building
Date: Sun, 19 Mar 2023 01:06:52 +0200 [thread overview]
Message-ID: <20230318230652.GB10144@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230318191747.3e5777db@coco.lan>
Hi Mauro,
On Sat, Mar 18, 2023 at 07:17:53PM +0100, Mauro Carvalho Chehab wrote:
> Em Tue, 14 Mar 2023 08:03:42 +0100 Gregor Jasny escreveu:
> > On 13.03.23 09:11, Laurent Pinchart wrote:
> > > If you want to give git-send-email another try (which is still the
> > > recommended option), https://git-send-email.io/ provides instructions
> > > tailored for different distributions and e-mail providers.
> >
> > I re-did the setup at home and it worked as expected. Turns out that
> > it's the company firewall which blocks git-send-email. Surprisingly
> > Thunderbird works with the same host and port.
> >
>
> Please revert it or fix it to build against Meson 0.56, as such change
> broke CI:
>
> https://builder.linuxtv.org/job/v4l-utils/
> https://builder.linuxtv.org/job/v4l-utils-coverity/
I've tested this simple patch and it seems to work fine for me:
diff --git a/meson.build b/meson.build
index 7b9ca7036b27..6443427486a9 100644
--- a/meson.build
+++ b/meson.build
@@ -1,6 +1,6 @@
project('v4l-utils', 'c', 'cpp',
version: '1.25.0',
- meson_version : '>= 0.57',
+ meson_version : '>= 0.56',
default_options : [
'buildtype=debugoptimized',
'warning_level=1',
My meson version is however newer. Could you test this with meson 0.56 ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-03-18 23:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:44 [v4l-utils] [PATCH v10 0/5] Switch build system to meson Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 1/5] Add support for meson building Laurent Pinchart
2023-03-12 14:31 ` Gregor Jasny
2023-03-12 14:49 ` Laurent Pinchart
2023-03-13 7:57 ` Gregor Jasny
2023-03-13 8:11 ` Laurent Pinchart
2023-03-14 7:03 ` Gregor Jasny
2023-03-18 18:17 ` Mauro Carvalho Chehab
2023-03-18 23:06 ` Laurent Pinchart [this message]
2023-03-19 0:20 ` Mauro Carvalho Chehab
2023-03-13 9:09 ` Sean Young
2023-03-13 10:15 ` Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 2/5] Copy Doxygen configuration file to doc/ Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 3/5] meson: Add support for doxygen documentation Laurent Pinchart
2023-03-20 11:38 ` Mauro Carvalho Chehab
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 4/5] Drop autoconf/automake support Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 5/5] meson: Use -include to include config.h instead of -I Laurent Pinchart
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=20230318230652.GB10144@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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