unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "D. Birch" <d.s.j.birch@gmail.com>, 53645@debbugs.gnu.org
Subject: bug#53645: Unable to guix pull on pinebook pro
Date: Mon, 31 Jan 2022 11:10:00 +0100	[thread overview]
Message-ID: <b396d93cfcbb10abec1935d5ba8a8a9b8ddc1654.camel@telenet.be> (raw)
In-Reply-To: <CAJw6i1B8MFaHR556bCEa0YkdP_K=jXYrtPkyatVBODBbNd8sQg@mail.gmail.com>

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

D. Birch schreef op zo 30-01-2022 om 20:36 [+0000]:
> As title.
> 
> I'm using a pinebook pro (arm64) and guix pull is giving up on me.
> 
> I've attached the output of stdout and stderr.
> 
> Did I do something wrong?

From guix-pull-bug:
> builder for `/gnu/store/5mqlzr4gs2f28c4i64rcbxs2zw2zzfzc-gcc-10.3.0.drv' failed with exit code 1
> build of /gnu/store/5mqlzr4gs2f28c4i64rcbxs2zw2zzfzc-gcc-10.3.0.drv failed
> View build log at '/var/log/guix/drvs/5m/qlzr4gs2f28c4i64rcbxs2zw2zzfzc-gcc-10.3.0.drv.bz2'.

The log /var/log/guix/drvs/5m/qlzr4gs2f28c4i64rcbxs2zw2zzfzc-gcc-10.3.0.drv.bz2
is required to investigate the issue.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-01-31 10:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 20:36 bug#53645: Unable to guix pull on pinebook pro D. Birch
2022-01-31 10:10 ` Maxime Devos [this message]
2022-01-31 18:58   ` D. Birch
2022-01-31 19:12     ` Maxime Devos
2022-01-31 19:57       ` Pierre Langlois
2022-02-02  8:47 ` D. Birch
2022-02-02 22:35   ` Pierre Langlois
2022-02-03 10:21     ` D. Birch
2022-02-03 15:56       ` Maxime Devos
2022-02-03 16:27         ` D. Birch
2022-02-03 16:36           ` D. Birch
2022-02-03 16:43           ` Maxime Devos

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=b396d93cfcbb10abec1935d5ba8a8a9b8ddc1654.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53645@debbugs.gnu.org \
    --cc=d.s.j.birch@gmail.com \
    /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).