From: rc-05 <rc-05@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: Gauche-0.9.9
Date: Sat, 25 Apr 2020 16:07:19 +0200 [thread overview]
Message-ID: <20200425140719.6VU5tiNCxQ3Mtmfmsf6QSLqQqB66AxJuNQ6cAnC5oJc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21205@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
New comment by rc-05 on void-packages repository
https://github.com/void-linux/void-packages/pull/21205#issuecomment-619385031
Comment:
> > Let's see if Travis CI can build at least for the archs with glibc runtime.
>
> I encourage you to look at build logs on travis to see what real problem is.
>
> For cross compilation, problem is that gosh is executed during build. When it is native built, a while-ago created binary can be used. When cross-built, it cannot, but one can install native gosh by adding to hostmakedepends.
>
> But if you simply add Gauche to hostmakedepends, there is need for Gauche to build Gauche. Solution is to only depend on Gauche in case of cross build, take a look for template of php.
Ok thanks! I'm going to follow your suggestions. Looking at the build logs it seems that it doesn't find the man page so it's a minor stuff that can be easily fixed
next prev parent reply other threads:[~2020-04-25 14:07 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:42 [PR PATCH] " rc-05
2020-04-21 16:29 ` [PR PATCH] [Updated] " rc-05
2020-04-21 16:42 ` rc-05
2020-04-21 16:44 ` rc-05
2020-04-21 19:52 ` Chocimier
2020-04-22 22:46 ` [PR PATCH] [Updated] " rc-05
2020-04-22 22:49 ` rc-05
2020-04-22 22:52 ` [PR PATCH] [Updated] " rc-05
2020-04-22 22:53 ` rc-05
2020-04-22 22:53 ` rc-05
2020-04-22 22:53 ` rc-05
2020-04-22 22:55 ` [PR PATCH] [Updated] " rc-05
2020-04-22 23:34 ` rc-05
2020-04-22 23:36 ` rc-05
2020-04-22 23:39 ` [PR PATCH] [Updated] " rc-05
2020-04-22 23:40 ` rc-05
2020-04-24 17:07 ` Chocimier
2020-04-25 14:06 ` rc-05
2020-04-25 14:07 ` rc-05 [this message]
2020-04-25 16:09 ` [PR PATCH] [Updated] " rc-05
2020-04-25 16:23 ` rc-05
2020-04-25 16:25 ` rc-05
2020-04-27 16:44 ` [PR PATCH] [Updated] " rc-05
2020-04-27 21:13 ` rc-05
2020-04-28 15:12 ` rc-05
2020-04-28 15:12 ` rc-05
2020-04-28 15:12 ` rc-05
2020-04-28 15:13 ` rc-05
2020-04-28 15:13 ` rc-05
2020-04-28 15:15 ` [PR PATCH] [Updated] " rc-05
2020-04-28 21:51 ` rc-05
2020-04-28 23:58 ` [PR PATCH] [Updated] " rc-05
2020-04-29 0:00 ` rc-05
2020-04-30 19:05 ` [WIP] " rc-05
2020-04-30 19:07 ` Chocimier
2020-04-30 19:08 ` Chocimier
2020-04-30 21:17 ` rc-05
2020-04-30 21:29 ` [PR PATCH] [Updated] " rc-05
2020-05-01 22:45 ` Chocimier
2020-05-03 21:55 ` rc-05
2020-05-03 21:57 ` rc-05
2020-05-03 22:03 ` rc-05
2020-05-03 22:05 ` [PR PATCH] [Updated] " rc-05
2020-05-03 22:06 ` rc-05
2020-05-03 22:07 ` rc-05
2020-05-03 22:08 ` rc-05
2020-05-04 18:00 ` Chocimier
2020-05-07 2:41 ` rc-05
2020-05-07 2:41 ` rc-05
2020-05-07 12:26 ` [PR PATCH] [Updated] " rc-05
2020-05-07 13:31 ` rc-05
2020-05-11 21:23 ` Chocimier
2020-05-11 21:55 ` rc-05
2020-05-16 11:57 ` Chocimier
2020-05-17 14:41 ` [PR PATCH] [Updated] " rc-05
2020-05-18 16:39 ` [PR PATCH] [Merged]: " Chocimier
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=20200425140719.6VU5tiNCxQ3Mtmfmsf6QSLqQqB66AxJuNQ6cAnC5oJc@z \
--to=rc-05@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).