From: "D. Birch" <d.s.j.birch@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53645@debbugs.gnu.org
Subject: bug#53645: Unable to guix pull on pinebook pro
Date: Mon, 31 Jan 2022 18:58:56 +0000 [thread overview]
Message-ID: <CAJw6i1DnsPGRVzdghBe9dGiFNQq9N0jMv1uunZkdjd3dXoThDg@mail.gmail.com> (raw)
In-Reply-To: <b396d93cfcbb10abec1935d5ba8a8a9b8ddc1654.camel@telenet.be>
[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]
Added. Thank-you.
On Mon, 31 Jan 2022, 10:10 Maxime Devos, <maximedevos@telenet.be> wrote:
> 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 #1.2: Type: text/html, Size: 1152 bytes --]
[-- Attachment #2: qlzr4gs2f28c4i64rcbxs2zw2zzfzc-gcc-10.3.0.drv.bz2 --]
[-- Type: application/bzip2, Size: 490618 bytes --]
next prev parent reply other threads:[~2022-01-31 19:44 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
2022-01-31 18:58 ` D. Birch [this message]
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=CAJw6i1DnsPGRVzdghBe9dGiFNQq9N0jMv1uunZkdjd3dXoThDg@mail.gmail.com \
--to=d.s.j.birch@gmail.com \
--cc=53645@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).