Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: golangci-lint: update to 1.23.1
Date: Tue, 21 Jan 2020 18:10:34 +0100	[thread overview]
Message-ID: <20200121171034.M-acxb2tiHRN6beGTB6QTyiq6AKj8vGUPD5SDwrvfTY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18405@inbox.vuxu.org>

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

New comment by renatoaguiar on void-packages repository

https://github.com/void-linux/void-packages/pull/18405#issuecomment-576782894

Comment:
> This fails to cross build for `arm*` and `aarch64*`. It succeeds for `ppc64le*` but fails for all other cross architectures and also for `i686-musl` here. I wonder if this a problem with the `go` build style or `go` itself.
> 
> I think `nocross="Fails to cross build for most targets"` would be a temporary solution.

I just tried cross-compiling using original version from master and it works fine, so it doesn't seem to be related to Go itself. Let me do more debugging before marking it broken.


  parent reply	other threads:[~2020-01-21 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 19:56 [PR PATCH] golangci-lint: update to 1.23.0 voidlinux-github
2020-01-21 15:24 ` voidlinux-github
2020-01-21 17:02 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-21 17:10 ` voidlinux-github [this message]
2020-01-22  5:03 ` [PR PATCH] [Updated] golangci-lint: update to 1.23.1 voidlinux-github
2020-01-22  5:06 ` voidlinux-github
2020-01-22  5:09 ` voidlinux-github
2020-01-22  5:09 ` voidlinux-github
2020-01-25  8:05 ` [PR PATCH] [Merged]: " 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=20200121171034.M-acxb2tiHRN6beGTB6QTyiq6AKj8vGUPD5SDwrvfTY@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).