unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Leo Famulari" <leo@famulari.name>
To: "Konrad Hinsen" <konrad.hinsen@fastmail.net>,
	"Christopher Baines via Development of GNU Guix and the GNU
	System distribution." <guix-devel@gnu.org>
Subject: Re: Any go expert willing to help with updating IPFS?
Date: Mon, 13 Dec 2021 09:52:56 -0500	[thread overview]
Message-ID: <960200f4-4ec7-49b7-bd61-ae7d3680d0ce@www.fastmail.com> (raw)
In-Reply-To: <m1r1ahaqnn.fsf@fastmail.net>

It's likely that you need to use a newer version of Go.

On Mon, Dec 13, 2021, at 02:51, Konrad Hinsen wrote:
> Hi Guix,
>
> the version of IPFS in Guix is 0.8, and in view of the important changes
> introduced in 0.10, that's obsolete by now. Which is why I am trying to
> update to 0.11.
>
> My current package definition is attached. It fails, but provides no
> clear hint (to the Go ignorant that I am) about what is actually going
> wrong:
>
>    starting phase `build'
>    
> src/github.com/ipfs/go-ipfs/vendor/github.com/lucas-clemente/quic-go/internal/qerr/error_codes.go:6:2: 
> build constraints exclude all Go files in 
> /tmp/guix-build-go-ipfs-0.11.0.drv-0/src/github.com/ipfs/go-ipfs/vendor/github.com/lucas-clemente/quic-go/internal/qtls
>    Building 'github.com/ipfs/go-ipfs/cmd/ipfs' failed.
>
> The build log then shows the results of `go env`, where nothing looks
> suspicious to me. Then another cryptic line:
>
>    command "go" "install" "-v" "-x" "-ldflags=-s -w" 
> "github.com/ipfs/go-ipfs/cmd/ipfs" failed with status 1
>
> Does anyone have an idea for debugging this issue?
>
> Cheers,
>   Konrad.


  parent reply	other threads:[~2021-12-13 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  7:51 Any go expert willing to help with updating IPFS? Konrad Hinsen
2021-12-13 10:01 ` Konrad Hinsen
2021-12-13 14:52 ` Leo Famulari [this message]
2021-12-13 15:37   ` Konrad Hinsen

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=960200f4-4ec7-49b7-bd61-ae7d3680d0ce@www.fastmail.com \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).