From: Jon Turney <jon.turney@dronecode.org.uk>
To: Tatsuro MATSUOKA <matsuoka@nuce.nagoya-u.ac.jp>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: meson build error on gedit-3.32.2
Date: Sun, 12 Jun 2022 17:29:17 +0100 [thread overview]
Message-ID: <91e02e78-f6d5-6094-4ada-b489bf8423e4@dronecode.org.uk> (raw)
In-Reply-To: <879744514.638572.1654667292450.JavaMail.yahoo@mail.yahoo.co.jp>
On 08/06/2022 06:48, Tatsuro MATSUOKA wrote:
> I am trying to build gedit-3.32.2 by meson.
May I ask, why did you choose that particular version?
> $ meson _build
> :
> <snip>
> :
> Program python3 found: YES (/usr/bin/python3)
> WARNING: Python files installed by Meson might not be found by python interpreter.
> This warning can be avoided by setting "python.platlibdir" option.
> WARNING: Python files installed by Meson might not be found by python interpreter.
> This warning can be avoided by setting "python.purelibdir" option.
> Configuring config.h using configuration
I can't reproduce this.
I think perhaps maybe you are encountering a meson bug (already fixed in
upstream) that this warning is emitted when you make an unusual choice
of prefix?
> data/meson.build:19:0: ERROR: Function does not take positional arguments.
To fix this error, you'll need to backport the patch from
https://gitlab.gnome.org/GNOME/gedit/-/merge_requests/124/diffs
> Please give me suggestions for setting "python.platlibdir" and "python.purelibdir" options.
next prev parent reply other threads:[~2022-06-12 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <879744514.638572.1654667292450.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-06-08 5:48 ` Tatsuro MATSUOKA
2022-06-12 16:29 ` Jon Turney [this message]
2022-06-13 0:33 ` Tatsuro MATSUOKA
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=91e02e78-f6d5-6094-4ada-b489bf8423e4@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=matsuoka@nuce.nagoya-u.ac.jp \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).