Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Cross arm*-musl hangs when runing g-ir-scanner-qemuwrapper
Date: Sat, 04 May 2019 23:12:08 +0200	[thread overview]
Message-ID: <20190504211208.mqDOY_61he2Qfjk4mICR05Rq0ofn4t_lqPO1fnaAhks@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11426@inbox.vuxu.org>

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

New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/issues/11426#issuecomment-489365964
Comment:
Hmm, maybe I’m not getting something, but in `/usr/bin/g-ir-scanner`

```
#!/usr/bin/env bash
# Check if we are running in an xbps-src environment and run the wrapper if that
# is the case.
if [ -n "$XBPS_CROSS_BASE" -a -n "$XBPS_TARGET_MACHINE" -a -n "$XBPS_VERSION" ]; then
	# This prevents g-ir-scanner from writing cache data to $HOME
	export GI_SCANNER_DISABLE_CACHE=1
	
	exec /usr/bin/g-ir-scanner.wrapped \
				 --use-binary-wrapper=/usr/bin/g-ir-scanner-qemuwrapper \
				 --use-ldd-wrapper=/usr/bin/g-ir-scanner-lddwrapper \
				 --add-include-path=${XBPS_CROSS_BASE}/usr/share/gir-1.0 \
				 --add-include-path=${XBPS_CROSS_BASE}/usr/lib/gir-1.0 \
				 "${@//-I\/usr\/include/-I${XBPS_CROSS_BASE}\/usr\/include}"
fi
	
exec /usr/bin/g-ir-scanner.wrapped "$@"
```

shouldn’t the last line belong to the ‘else’ branch of the if clause? Else there are two `exec`s in the cross case.
Same with `g-ir-compiler`.

  parent reply	other threads:[~2019-05-04 21:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11426@inbox.vuxu.org>
2019-05-04 12:46 ` voidlinux-github
2019-05-04 14:03 ` voidlinux-github
2019-05-04 19:34 ` voidlinux-github
2019-05-04 19:52 ` voidlinux-github
2019-05-04 19:59 ` voidlinux-github
2019-05-04 20:41 ` voidlinux-github
2019-05-04 21:12 ` voidlinux-github [this message]
2019-05-05  2:08 ` voidlinux-github
2019-05-05  4:41 ` voidlinux-github
2019-05-05 13:18 ` voidlinux-github
2019-05-05 13:33 ` voidlinux-github
2019-05-05 14:00 ` voidlinux-github
2019-05-05 16:07 ` voidlinux-github
2019-05-05 16:19 ` voidlinux-github
2019-05-05 16:24 ` voidlinux-github
2019-05-05 16:27 ` voidlinux-github
2019-05-05 16:31 ` voidlinux-github
2019-05-05 16:59 ` voidlinux-github
2019-05-05 17:08 ` voidlinux-github
2019-05-05 18:39 ` voidlinux-github
2019-05-05 18:54 ` voidlinux-github
2019-05-05 19:04 ` voidlinux-github
2019-05-05 19:25 ` voidlinux-github
2019-05-05 19:25 ` voidlinux-github
2019-05-05 19:40 ` voidlinux-github
2019-05-05 19:40 ` voidlinux-github
2019-05-05 19:51 ` voidlinux-github
2019-05-05 20:11 ` voidlinux-github
2019-05-07 13:20 ` voidlinux-github
2019-05-07 13:24 ` voidlinux-github
2019-07-01 12:31 ` [ISSUE] [CLOSED] " voidlinux-github

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=20190504211208.mqDOY_61he2Qfjk4mICR05Rq0ofn4t_lqPO1fnaAhks@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).