From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: pinta-1.7
Date: Tue, 19 Jan 2021 08:56:31 +0100 [thread overview]
Message-ID: <20210119075631.zXJgW0DSES18eoh4Q8zjGhKakN0uG5PBkYtXCk5XNcc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27787@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/27787#issuecomment-762668212
Comment:
On crossbuild, tested via `./xbps-src pkg -a aarch64-musl mono-addins`, it complains about:
```
Running autoconf ...
Running ./configure ...
checking for a BSD-compatible install... /builddir/.xbps-mono-addins/wrappers/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... none
checking whether to enable maintainer-specific portions of Makefiles... yes
checking pkg-config is at least version 0.16... yes
checking for mcs... no
configure: error: mcs Not found
=> ERROR: mono-addins-1.3_1: pre_configure: './autogen.sh' exited with 1
=> ERROR: in pre_configure() at srcpkgs/mono-addins/template:18
```
It's failing to find mcs? Doing `xlocate /usr/bin/mcs` returns `mono-6.12.0.107_1 /usr/bin/mcs`. Mono IS in `depends` and `mono-devel` is in `makedepends`. Is it appropriate to do something like `nocross="mcs not available on cross platform"`?
next prev parent reply other threads:[~2021-01-19 7:56 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 18:52 [PR PATCH] " kawaiiamber
2021-01-15 21:35 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-18 15:35 ` not-chicken
2021-01-18 21:02 ` kawaiiamber
2021-01-18 21:35 ` not-chicken
2021-01-19 0:31 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 0:32 ` kawaiiamber
2021-01-19 7:22 ` not-chicken
2021-01-19 7:27 ` [PR REVIEW] " not-chicken
2021-01-19 7:27 ` not-chicken
2021-01-19 7:27 ` not-chicken
2021-01-19 7:30 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 7:31 ` [PR REVIEW] " kawaiiamber
2021-01-19 7:31 ` kawaiiamber
2021-01-19 7:33 ` kawaiiamber
2021-01-19 7:35 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 7:36 ` [PR REVIEW] " kawaiiamber
2021-01-19 7:37 ` not-chicken
2021-01-19 7:37 ` kawaiiamber
2021-01-19 7:40 ` [PR REVIEW] " kawaiiamber
2021-01-19 7:49 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 7:50 ` [PR REVIEW] " kawaiiamber
2021-01-19 7:51 ` kawaiiamber
2021-01-19 7:53 ` [PR REVIEW] " kawaiiamber
2021-01-19 7:56 ` kawaiiamber [this message]
2021-01-19 7:58 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 7:59 ` kawaiiamber
2021-01-19 8:05 ` kawaiiamber
2021-01-19 8:07 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 8:08 ` kawaiiamber
2021-01-19 8:09 ` not-chicken
2021-01-19 8:16 ` kawaiiamber
2021-01-19 8:17 ` kawaiiamber
2021-01-19 8:20 ` not-chicken
2021-01-19 8:22 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 8:23 ` kawaiiamber
2021-01-19 8:28 ` not-chicken
2021-01-19 8:30 ` kawaiiamber
2021-01-19 8:33 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 8:33 ` kawaiiamber
2021-01-19 8:55 ` not-chicken
2021-01-19 8:58 ` not-chicken
2021-01-19 8:59 ` not-chicken
2021-01-19 8:59 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-19 9:02 ` kawaiiamber
2021-01-19 9:12 ` not-chicken
2021-01-19 9:24 ` kawaiiamber
2021-01-19 9:35 ` not-chicken
2021-03-18 18:45 ` [PR PATCH] [Updated] " kawaiiamber
2021-03-18 18:46 ` [PR REVIEW] " kawaiiamber
2021-08-09 18:28 ` ericonr
2022-02-04 10:32 ` [PR REVIEW] " meator
2022-05-06 2:08 ` github-actions
2022-05-20 2:11 ` [PR PATCH] [Closed]: " github-actions
2022-05-20 2:54 ` kawaiiamber
2022-05-20 13:18 ` kawaiiamber
2022-08-19 2:16 ` github-actions
2022-09-03 2:14 ` [PR PATCH] [Closed]: " github-actions
2022-09-27 23:37 ` mjeveritt
2022-09-27 23:45 ` mjeveritt
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=20210119075631.zXJgW0DSES18eoh4Q8zjGhKakN0uG5PBkYtXCk5XNcc@z \
--to=kawaiiamber@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).