Github messages for voidlinux
 help / color / mirror / Atom feed
From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [tracking] List of currently failing builds
Date: Sat, 03 Sep 2022 18:37:00 +0200	[thread overview]
Message-ID: <20220903163700.zaD4z3t-RmIxqXC3eqq24lTEyLWAHTnDLfQtXHx4jGA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39083@inbox.vuxu.org>

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

New comment by CameronNemo on void-packages repository

https://github.com/void-linux/void-packages/issues/39083#issuecomment-1236160344

Comment:
Also when trying to get a useful build log from failing go packages, you probably want to set XBPS_MAKEJOBS=1 so that the error is the last log message (or close to it). Multiple jobs typically causes the error to get lost in the shuffle of logs.

For example this is the syncthing log I got:

<details>
  <summary>log</summary>

 ```
=> syncthing-1.20.4_1: running do_build ...
WORK=/tmp/go-build3356811540
mkdir -p $WORK/b337/
cat >$WORK/b337/importcfg << 'EOF' # internal
# import config
packagefile crypto=/usr/lib/go/pkg/linux_amd64/crypto.a
packagefile crypto/cipher=/usr/lib/go/pkg/linux_amd64/crypto/cipher.a
packagefile crypto/tls=/host/gocache-glibc/3b/3be91765b0cd9a80c809f19b94dd68417dc956f9e4f0f268f2c71891d108d0f2-d
packagefile github.com/marten-seemann/qtls-go1-18=/host/gocache-glibc/53/535e785ace1b5b21edab486fa8ffc6d61ebf334dd5a131445523cea347d10931-d
packagefile net=/host/gocache-glibc/6a/6a24ec9242586a43d069abb6ff06ce7b50b4b4876a95ec785bf7ebd9cd4fec13-d
EOF
cd /builddir/syncthing-1.20.4
/usr/lib/go/pkg/tool/linux_amd64/compile -o $WORK/b337/_pkg_.a -trimpath "$WORK/b337=>" -p github.com/lucas-clemente/quic-go/internal/qtls -lang=go1.16 -complete -buildid Omu6ayi7ABK4vInTcMyh/Omu6ayi7ABK4vInTcMyh -goversion go1.19 -c=12 -nolocalimports -importcfg $WORK/b337/importcfg -pack ./_build-syncthing-xbps/pkg/mod/github.com/lucas-clemente/quic-go@v0.27.0/internal/qtls/go118.go ./_build-syncthing-xbps/pkg/mod/github.com/lucas-clemente/quic-go@v0.27.0/internal/qtls/go119.go
# github.com/lucas-clemente/quic-go/internal/qtls
_build-syncthing-xbps/pkg/mod/github.com/lucas-clemente/quic-go@v0.27.0/internal/qtls/go119.go:6:13: cannot use "The version of quic-go you're using can't be built on Go 1.19 yet. For more details, please see https://github.com/lucas-clemente/quic-go/wiki/quic-go-and-Go-versions." (untyped string constant "The version of quic-go you're using can't be built on Go 1.19 yet. F...) as int value in variable declaration
=> ERROR: syncthing-1.20.4_1: do_build: 'go install -p "$XBPS_MAKEJOBS" -mod="${go_mod_mode}" -x -tags "${go_build_tags}" -ldflags "${go_ldflags}" ${go_package}' exited with 2
=> ERROR:   in do_build() at common/build-style/go.sh:43
```

</details>

  parent reply	other threads:[~2022-09-03 16:37 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03  9:46 [ISSUE] " paper42
2022-09-03  9:47 ` paper42
2022-09-03 12:06 ` sgn
2022-09-03 12:06 ` sgn
2022-09-03 16:31 ` CameronNemo
2022-09-03 16:33 ` CameronNemo
2022-09-03 16:37 ` CameronNemo [this message]
2022-09-03 16:40 ` CameronNemo
2022-09-03 17:04 ` oreo639
2022-09-03 17:08 ` oreo639
2022-09-03 17:35 ` oreo639
2022-09-03 17:42 ` oreo639
2022-09-03 18:02 ` oreo639
2022-09-03 18:07 ` paper42
2022-09-03 18:08 ` paper42
2022-09-03 18:18 ` paper42
2022-09-04  8:57 ` sgn
2022-09-04 14:30 ` sgn
2022-09-04 15:15 ` sgn
2022-09-04 15:24 ` sgn
2022-09-04 18:04 ` sgn
2022-09-05 15:59 ` classabbyamp
2022-09-05 15:59 ` classabbyamp
2022-09-06 15:11 ` mtboehlke
2022-09-06 16:33 ` paper42
2022-09-06 16:33 ` paper42
2022-09-07 10:32 ` paper42
2022-09-22 14:29 ` mtboehlke
2022-09-29 16:05 ` TeddyDD
2022-09-29 18:41 ` paper42
2022-09-29 19:34 ` paper42
2022-09-29 19:38 ` paper42
2022-10-02 20:56 ` motorto
2022-10-05  8:07 ` paper42
2022-10-08 21:12 ` paper42
2022-10-08 21:13 ` paper42
2022-10-08 21:13 ` paper42
2022-10-08 21:14 ` paper42
2022-10-08 21:14 ` paper42
2022-10-08 21:15 ` paper42
2022-10-08 21:30 ` paper42
2022-10-08 21:31 ` paper42
2022-11-17 14:32 ` tranzystorek-io
2022-11-26 18:35 ` kruceter
2022-11-26 21:14 ` kruceter
2022-11-30 17:53 ` kruceter
2022-12-04 16:39 ` kruceter
2022-12-25 18:13 ` mhmdanas
2022-12-25 18:32 ` kruceter
2022-12-25 18:38 ` CameronNemo
2022-12-25 20:29 ` mhmdanas
2022-12-25 20:29 ` mhmdanas
2022-12-25 20:30 ` mhmdanas
2022-12-25 20:32 ` mhmdanas
2022-12-25 20:33 ` mhmdanas
2022-12-25 20:43 ` mhmdanas
2022-12-25 20:43 ` mhmdanas
2023-01-06 12:26 ` kruceter
2023-01-21 19:52 ` r-ricci
2023-02-09 21:23 ` dkwo
2023-02-15  1:48 ` dkwo
2023-04-03 13:21 ` zlice
2023-04-03 13:35 ` zlice
2023-04-03 14:25 ` zlice
2023-04-18 20:37 ` mhmdanas
2023-04-19 21:32 ` mhmdanas
2023-07-25 19:20 ` dkwo
2023-07-25 20:12 ` TeddyDD
2023-07-25 20:33 ` dkwo
2023-07-25 21:47 ` TeddyDD
2023-07-26  5:29 ` TeddyDD
2023-10-21 11:13 ` motorto
2023-10-21 13:06 ` zlice
2023-10-21 17:12 ` motorto
2023-11-10 20:26 ` vfx1b
2023-11-10 22:09 ` vfx1b
2023-11-10 22:15 ` classabbyamp
2023-11-13 16:47 ` vfx1b
2023-11-14 13:39 ` zlice
2023-11-14 13:40 ` zlice
2023-11-14 13:41 ` zlice
2024-03-23 16:17 ` adigitoleo
2024-03-23 17:22 ` leahneukirchen

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=20220903163700.zaD4z3t-RmIxqXC3eqq24lTEyLWAHTnDLfQtXHx4jGA@z \
    --to=cameronnemo@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).