From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 29824@debbugs.gnu.org, Peter Mikkelsen <petermikkelsen10@gmail.com>
Subject: bug#29824: Meson 0.44.0 is broken with guix.
Date: Tue, 09 Jan 2018 13:46:23 +0100 [thread overview]
Message-ID: <87bmi3td28.fsf@gnu.org> (raw)
In-Reply-To: <1a5a9106-e648-11ef-9880-8157eb1399f0@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 2 Jan 2018 16:52:18 +0100")
Hi Hartmut,
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> We need to have a look at the whole `detect_meson_py_location()`, not
> only on lines 47 to 51.
>
> detect_meson_py_location() assumes the executable to be called "meson"
> or "meson.py", but in guix it currently is called ".meson-real" (see teh
> first entry in the trace-back).
>
> The solution would be to get rid of the wrapper-scripts, see
> <https://lists.gnu.org/archive/html/guix-devel/2017-11/msg00041.html>
>
> A work-around would be to substitute in file mesonbuild/mesonlib.py
>
> meson_command = python_command + [detect_meson_py_location()]
>
> by
>
> meson_command = python_command + ["$OUT/bin/meson"]
Sounds reasonable. Does it work for you? If so, could you provide a
patch?
Ludo’.
next prev parent reply other threads:[~2018-01-09 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 19:18 bug#29824: Meson 0.44.0 is broken with guix Fis Trivial
2018-01-02 15:52 ` Hartmut Goebel
2018-01-09 12:46 ` Ludovic Courtès [this message]
2018-01-09 21:10 ` Hartmut Goebel
[not found] ` <CADh9keUUZNYBd7-doGcL1O9+bMdxtVK=PzVFL-9_MSUPWF7_=A@mail.gmail.com>
[not found] ` <CADh9keWM+hyLV=ffDx7XDWQFLS9O4tEtBEJ3aQzHPQBX-yRfjw@mail.gmail.com>
2018-01-09 23:34 ` Peter Mikkelsen
2018-01-14 20:06 ` Fis Trivial
2018-01-14 20:14 ` Fis Trivial
2018-01-14 22:02 ` Ludovic Courtès
2020-09-28 13:00 ` zimoun
2020-11-30 16:14 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmi3td28.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29824@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=petermikkelsen10@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).