From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: Guix Help <help-guix@gnu.org>
Subject: Packaging Proton Bridge: cryptic compilation failure
Date: Sat, 30 Nov 2024 17:26:58 +0100 [thread overview]
Message-ID: <2208743.irdbgypaU6@aisaka> (raw)
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
Hello Guix
I am towards the end of a first pass of packaging the Proton Bridge program to
access my Proton Mail with KMail.
I have worked through and learned about many peculiarities of Golang build
system. As long as I had an error message, I was able to at least work around
problems. However, the latest build failure is completely cryptic to me, as
its log contains zero error messages. It works fine until I get a "build
failed" summary:
[...]
/gnu/store/kw4dwavpd5638kxaxnyhchzbip2ihr7q-go-1.21.5/lib/go/pkg/tool/
linux_amd64/compile -o ./go-build882385907/b247/_pkg_.a -trimpath "/tmp/guix-
build-go-github-com-protonmail-go-proton-api-0.4.0.drv-0/src/golang.org/x/
text/encoding/ianaindex=>golang.org/x/text/encoding/ianaindex;$WORK/b247=>" -p
golang.org/x/text/encoding/ianaindex -complete -buildid oeeEgL1OtT44tPEiSSgm/
oeeEgL1OtT44tPEiSSgm -goversion go1.21.5 -nolocalimports -importcfg ./go-
build882385907/b247/importcfg -pack ./src/golang.org/x/text/encoding/
ianaindex/ascii.go ./src/golang.org/x/text/encoding/ianaindex/ianaindex.go ./
src/golang.org/x/text/encoding/ianaindex/tables.go
/gnu/store/kw4dwavpd5638kxaxnyhchzbip2ihr7q-go-1.21.5/lib/go/pkg/tool/
linux_amd64/buildid -w $WORK/b247/_pkg_.a # internal
cp $WORK/b247/_pkg_.a /tmp/guix-build-go-github-com-protonmail-go-proton-
api-0.4.0.drv-0/go-build/
59/59c52b9f8132289a5cc9772aa1edea166f986e6eb6d79cd07cbaac8bcbf28c75-d #
internal
Building 'github.com/ProtonMail/go-proton-api' failed.
[...]
The above is the result of this command:
$ guix build -v 3 -L ~/repositories/sovereign/ proton-bridge --cores=1
I have zero knowledge the Go language itself, which could explain why I have
trouble understanding this failure.
I would very much appreciate any help from the resident Go packagers, as I am
unable to make any further progress, and I desire to finally ditch the
Proton’s web interface.
The entire package code is on my personal channel, in "proton-bridge" branch.
There is one external dependency on the Efraim’s DFSG channel.
CGIT interface:
https://git.marekpasnikowski.pl/sovereign.git/tree/?h=proton-bridge
GIT clone URL:
https://git.marekpasnikowski.pl/sovereign.git
DFSG channel:
https://git.sr.ht/~efraim/my-guix
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-11-30 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 16:26 Marek Paśnikowski [this message]
2024-11-30 17:29 ` Packaging Proton Bridge: cryptic compilation failure Ian Eure
2024-11-30 18:08 ` Cayetano Santos
2024-11-30 18:56 ` Marek Paśnikowski
2024-11-30 19:22 ` Ian Eure
2024-12-05 16:37 ` sebastien
2024-12-06 13:34 ` woshilapin
2024-12-06 18:01 ` Marek Paśnikowski
2024-12-09 16:24 ` Packaging Proton Bridge: Progress Report #1 Marek Paśnikowski
2024-12-09 16:38 ` Ian Eure
2024-12-09 16:47 ` Marek Paśnikowski
2024-12-09 16:52 ` Ian Eure
2024-12-09 19:15 ` Marek Paśnikowski
2024-12-09 19:33 ` Ian Eure
2024-12-10 10:28 ` Packaging Proton Bridge: Progress Report #2 Marek Paśnikowski
2024-12-10 14:08 ` Suhail Singh
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=2208743.irdbgypaU6@aisaka \
--to=marek@marekpasnikowski.pl \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).