Github messages for voidlinux
 help / color / Atom feed
From: pullmoll <>
Subject: [ISSUE] NetworkManager: wrong meson exe_wrapper for mips*hf
Date: Sun, 22 Mar 2020 12:35:07 +0100
Message-ID: <> (raw)

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

New issue by pullmoll on void-packages repository

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/ --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/ /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/`:
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.

             reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 11:35 pullmoll [this message]
2020-03-23  7:14 ` sgn
2020-03-23 15:40 ` sgn
2020-03-23 15:44 ` sgn
2020-03-23 21:58 ` [ISSUE] [CLOSED] " pullmoll

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Github messages for voidlinux

Archives are clonable: git clone --mirror

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone