From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/meson: bump version to 0.50.0
Date: Thu, 21 Mar 2019 20:06:32 +0100 [thread overview]
Message-ID: <20190321200632.4dee85b7@gmx.net> (raw)
In-Reply-To: <20190319223422.64ba1be0@windsurf>
Hello Thomas,
On Tue, 19 Mar 2019 22:34:22 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello Peter,
>
> On Mon, 18 Mar 2019 22:43:24 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > package/meson/meson.hash | 4 ++--
> > package/meson/meson.mk | 2 +-
> > 2 files changed, 3 insertions(+), 3 deletions(-)
>
> I think this change broke the build of at-spi2-core:
>
> http://autobuild.buildroot.net/?reason=at-spi2-core-2.28.0
>
> it is using meson, and it started failing to build on March 19, i.e not
> long after I merged the meson bump. The log also says:
>
> WARNING: Project targetting '>= 0.40.1' but tried to use feature introduced in '0.50.0': install arg in configure_file
> Configuring atspi-2.pc using configuration
>
> atspi/meson.build:60:0: ERROR: Subdir keyword must not be an absolute path.
>
> I think we need to backport
> https://github.com/GNOME/at-spi2-core/commit/44a812ea51223d82f21a098a2d45fcc5c329ce7a.patch
> from upstream.
Yes, the patch fixes the problem for meson 0.50.0, will send an (already
outdated because of the meson bump revert) patch....
Nevertheless thanks for report and investigation...
Regards,
Peter
>
> Best regards,
>
> Thomas
prev parent reply other threads:[~2019-03-21 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 21:43 [Buildroot] [PATCH v1] package/meson: bump version to 0.50.0 Peter Seiderer
2019-03-18 22:00 ` Thomas Petazzoni
2019-03-19 21:34 ` Thomas Petazzoni
2019-03-21 19:06 ` Peter Seiderer [this message]
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=20190321200632.4dee85b7@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.