Github messages for voidlinux
 help / color / mirror / Atom feed
From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] NetworkManager: wrong meson exe_wrapper for mips*hf
Date: Mon, 23 Mar 2020 22:58:39 +0100	[thread overview]
Message-ID: <20200323215839.xK7-bkJ3uYrPoT3oZuK6z7C3lK7Zq3wUijC99q46lXM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20281@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

Closed issue by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20281

Description:
I don't know how this can happen as we have not set this value anywhere, but this is what happens when trying to build `NetworkManager` for `mips*`:
```
[682/692] Generating nm-property-docs.xml with a custom command.
FAILED: libnm/nm-property-docs.xml 
env -i GI_TYPELIB_PATH=/builddir/NetworkManager-1.22.6/build/libnm LD_LIBRARY_PATH=/builddir/NetworkManager-1.22.6/build/libnm sh -c '/usr/bin/qemu-mipselhf-static -L /usr/mipsel-linux-muslhf /usr/mipsel-linux-muslhf/bin/python3' /builddir/NetworkManager-1.22.6/libnm/generate-setting-docs.py --lib-path /builddir/NetworkManager-1.22.6/build/libnm --gir libnm/NM-1.0.gir --output libnm/nm-property-docs.xml
/builddir/NetworkManager-1.22.6/libnm/generate-setting-docs.py: /usr/bin/qemu-mipselhf-static: No such file or directory
```

See it tries to use a `qemu-mipselhf-static` which does not exist. The correct arch to use here is `qemu-mipsel-static` and it is what can be found in `common/cross-profiles/mipselhf.sh`:
```
XBPS_TARGET_QEMU_MACHINE="mipsel"
```
I even tried to explicitly set `-Dexe_wrapper=qemu-${XBPS_TARGET_QEMU_MACHINE}-static` in `NetworkManager`'s `configure_args` yet it insists to use the wrong name.

I really wonder where this wrapper name is constructed, it seems from the cross triplet by stripping `-linux-musl`,  and why`this happens.


      parent reply	other threads:[~2020-03-23 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 11:35 [ISSUE] " pullmoll
2020-03-23  7:14 ` sgn
2020-03-23 15:40 ` sgn
2020-03-23 15:44 ` sgn
2020-03-23 21:58 ` pullmoll [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=20200323215839.xK7-bkJ3uYrPoT3oZuK6z7C3lK7Zq3wUijC99q46lXM@z \
    --to=pullmoll@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).