From: manfredu <manfredu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnucash: update to 4.4
Date: Sat, 02 Jan 2021 14:13:57 +0100 [thread overview]
Message-ID: <20210102131357.3JwRv_z_tmwvP6wKA_IoR449ypCu3VCWgnpcKd5jS_o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27504@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
New comment by manfredu on void-packages repository
https://github.com/void-linux/void-packages/pull/27504#issuecomment-753472149
Comment:
> The checks fail because they try to execute `make check` and it seems most of the test binaries are not available. To make them pass, it would be necessary to find out what is missing for the build process to build the tests and make sure they are compiled in the build process.
What does the third parameter in "Build packages (x86_64, x86_64, 1)" mean? For the builds where it is set to 0 the build succeeds.
next prev parent reply other threads:[~2021-01-02 13:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 16:34 [PR PATCH] gnucash: update to 4.3 manfredu
2020-12-28 19:53 ` unspecd
2020-12-29 21:37 ` [PR PATCH] [Updated] " manfredu
2020-12-31 9:41 ` gnucash: update to 4.4 Hoshpak
2021-01-02 13:13 ` manfredu [this message]
2021-01-03 5:51 ` fosslinux
2021-01-03 10:40 ` manfredu
2021-01-03 12:35 ` manfredu
2021-01-03 12:37 ` [PR PATCH] [Updated] " manfredu
2021-01-03 12:45 ` [WIP] " manfredu
2021-01-03 19:12 ` [PR PATCH] [Updated] " manfredu
2021-01-03 19:19 ` manfredu
2021-01-03 23:22 ` fosslinux
2021-02-04 22:13 ` [PR PATCH] [Updated] " manfredu
2021-02-04 23:38 ` manfredu
2021-02-06 19:04 ` manfredu
2021-02-06 23:02 ` manfredu
2021-02-06 23:04 ` pullmoll
2021-02-06 23:28 ` [PR PATCH] [Updated] " manfredu
2021-02-06 23:50 ` manfredu
2021-02-07 10:27 ` [PR PATCH] [Merged]: " Hoshpak
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=20210102131357.3JwRv_z_tmwvP6wKA_IoR449ypCu3VCWgnpcKd5jS_o@z \
--to=manfredu@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).