(address . bug-guix@gnu.org)
CAJw6i1B8MFaHR556bCEa0YkdP_K=jXYrtPkyatVBODBbNd8sQg@mail.gmail.com
Unable to guix pull on pinebook pro
- Open
Details
- 3 participants
- D. Birch
- Maxime Devos
- Pierre Langlois
- Owner
- unassigned
- Submitted by
- D. Birch
- Severity
- normal
D
M
b396d93cfcbb10abec1935d5ba8a8a9b8ddc1654.camel@telenet.be
D. Birch schreef op zo 30-01-2022 om 20:36 [+0000]:
Toggle quote (8 lines)
> 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:
Toggle quote (4 lines)
> 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.
M
(name . D. Birch)(address . d.s.j.birch@gmail.com)(address . 53645@debbugs.gnu.org)
f12ec0c99191a260c2d213a9b52de4975cf6be17.camel@telenet.be
I took a look but I don't know what's up with
Toggle quote (3 lines)
> g++ [...] -o cc1 [...]
> collect2: fatal error: ld terminated with signal 9 [Killed]
Seems like the linking step failed somehow?
Greetings,
Maxime.
D
(name . Maxime Devos)(address . maximedevos@telenet.be)(address . 53645@debbugs.gnu.org)
CAJw6i1DnsPGRVzdghBe9dGiFNQq9N0jMv1uunZkdjd3dXoThDg@mail.gmail.com
Added. Thank-you.
On Mon, 31 Jan 2022, 10:10 Maxime Devos, <maximedevos@telenet.be> wrote:
Toggle quote (24 lines)
> 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.
>
P
(name . D. Birch)(address . d.s.j.birch@gmail.com)
871r0nhdtf.fsf@gmx.com
Hi there,
Maxime Devos <maximedevos@telenet.be> writes:
Toggle quote (8 lines)
> [[PGP Signed Part:Undecided]]
> I took a look but I don't know what's up with
>
>> g++ [...] -o cc1 [...]
>> collect2: fatal error: ld terminated with signal 9 [Killed]
>
> Seems like the linking step failed somehow?
I would guess that the build ran out of memory, that can happen with the
pinebookpro's mere 4G. Do you have some swap space allocated? I've had
to do that on my rockpro64 (same chip) for guix pull to eventually
succeed.
Here's an example to create a quick swapfile in case you're not
familiar, as root:
# Create 10G
dd if=/dev/zero of=/mnt/swapfile bs=1MiB count=10240
# Enable it
chmod 600 /mnt/swapfile
mkswap /mnt/swapfile
swapon /mnt/swapfile
Hope this helps! Ideally you wouldn't have to build so much, but I'm
afraid we don't have aarch64 substitutes ready at the moment :-/.
Cheers,
Pierre
-----BEGIN PGP SIGNATURE-----
iQFMBAEBCgA2FiEEctU9gYy29KFyWDdMqPyeRH9PfVQFAmH4QM0YHHBpZXJyZS5s
YW5nbG9pc0BnbXguY29tAAoJEKj8nkR/T31UJH4IALnBBPOgexdJAbLBecIqmPtj
Y7LhHuHmQiQ9dT8rZRdBitQJThS3XEoEniKJOL+mdz+4NHsE8uKerJHRdutOFW6n
SANNaBQcksRUG+SS/JdZ+xWBbdkvbHv6hUWXko5cTYr7mKnUBhrfq1HzgZrZwuPg
B59A1bIQyIZTjygauHPEgv9UUNJCwcolLSBD9i93wFXELAyEbONaC6fLvA+HqAkW
v1gi40Li3E5q6g/P3ZEBKANRaizexpjOfvrvbLe4+g7m2KynsO/UGC21bWGxuCH2
ovB0Cb9hg6siJUDlyRvPvYfojzMh9TorRLTBGlVWaZQg9fi/T/sQYYXWKt1soMY=
=BaXt
-----END PGP SIGNATURE-----
D
Unable to guix pull on pinebook pro
(address . 53645@debbugs.gnu.org)
CAJw6i1CZa0eG+pf3rk7q6nbcB7vGgW95uMGg1NXf-5DH=ue-zQ@mail.gmail.com
Thank-you for all the help.
I left the laptop ticking away again after adding 10G of swap.
I've attached the stdout and stderr, as before.
Things got much further and the system was building for the whole day, I
left it running overnight and in the morning hit another "bug".
I can't see where the build log is this time to attach.
I don't fully understand what guix pull does. If I was to run it again,
would everything begin from the start, or is there some chance re-running
it would pick up where it left off?
I'll try it shortly and find out I suppose.
P
(name . D. Birch)(address . d.s.j.birch@gmail.com)
874k5gvqj7.fsf@gmx.com
Hi,
"D. Birch" <d.s.j.birch@gmail.com> writes:
Toggle quote (10 lines)
> Thank-you for all the help.
>
> I left the laptop ticking away again after adding 10G of swap.
>
> I've attached the stdout and stderr, as before.
>
> Things got much further and the system was building for the whole day, I left it running overnight and in the morning hit another "bug".
>
> I can't see where the build log is this time to attach.
That's strange that there isn't a log file to report, it looks like
util-linux didn't build but I'm not sure. What you could try is to run
`guix pull -v3' to enable more verbosity, and it should show build
output for packages as it's building them.
Toggle quote (2 lines)
> I don't fully understand what guix pull does. If I was to run it again, would everything begin from the start, or is there some chance re-running it would pick up where it left off?
Yeah, luckily guix pull should pickup where it left off and not rebuild
packages that are already built and present in /gnu/store. So normally,
you should only have to go through the couple of days of building once
(Well actually, in normal times we should have binary substitutes that
guix pull can download instead of building them, but the CI is having
issues with aarch64 at the moment :-/.).
That being said, new commits could be pushed and cause new rebuilds
between guix pull invokation, what you can do is pull a specific commit
first:
guix pull -v3 --commit=2641621 # Commit picked from the log file.
Hope that helps!
Thanks,
Pierre
-----BEGIN PGP SIGNATURE-----
iQFMBAEBCgA2FiEEctU9gYy29KFyWDdMqPyeRH9PfVQFAmH7COwYHHBpZXJyZS5s
YW5nbG9pc0BnbXguY29tAAoJEKj8nkR/T31UIBkIAKvaWL5eED7PU/8erjtVcWgz
FlqrykccZRbW/CCgO/ejFjU51pUZaiTm8BYuuRPd82N8ZFo4IzzadBFN6GCWvj6i
5CSsQ2Al+Z2u21pL4tsWaqefgm/iTvDoMeg1SGFImwVKXfcPspLJtqQ/7lSYE3iq
xm1qN+WImR4Uk0PrJpnLMbHjd4WL5Txssa+Gm5fumbpfEBUHQoszGTOby/utB2kM
dZ4sSBiRS0OJcGVtnF/DdKcilggC3FnJKgpGMuqJZL0aYgvnAxGv4aNn0PJUCdtG
esJ/pknJtMLhRfSOMRAtglVEui7fipSeeeii2+zImihnxCwAEYrq5pJry5inSiE=
=KfH/
-----END PGP SIGNATURE-----
D
(name . Pierre Langlois)(address . pierre.langlois@gmx.com)
CAJw6i1BOpFtgPLuO4mdjW-Nqdj+7RJnfhhk=CrBq+v43r4W9Fw@mail.gmail.com
On Wed, 2 Feb 2022 at 22:42, Pierre Langlois <pierre.langlois@gmx.com>
wrote:
Toggle quote (7 lines)
> That's strange that there isn't a log file to report, it looks like
> util-linux didn't build but I'm not sure. What you could try is to run
> `guix pull -v3' to enable more verbosity, and it should show build
> output for packages as it's building them.
> ...
> guix pull -v3 --commit=2641621 # Commit picked from the log file.
Tried my best not to top post ;)
I've attached the output from an attempt using a slight modification to the
command recommended above. The command I ran was
guix pull -v3 --commit=2641621 2>&1 | tee guix-pull-bug-verbose-01
Thank-you
M
(address . 53645@debbugs.gnu.org)
f8f7efc0b65ead81ad878fa4ddd4037a1bd9a73d.camel@telenet.be
This test is failing:
misc: swaplabel ... FAILED (misc/swaplabel)
This looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996764.
Debian even has a patch!
Or the cause could be different ...
Greetings,
Maxime.
D
(name . Maxime Devos)(address . maximedevos@telenet.be)
CAJw6i1DPd6FNmTM-=VZEU_BTSTCBu=37AQ2Z3d5zc7=4wx+eKQ@mail.gmail.com
On Thu, 3 Feb 2022 at 15:56, Maxime Devos <maximedevos@telenet.be> wrote:
Toggle quote (15 lines)
> This test is failing:
>
> misc: swaplabel ... FAILED
> (misc/swaplabel)
>
> This looks like <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996764
> >.
> Debian even has a patch!
>
> Or the cause could be different ...
>
> Greetings,
> Maxime.
>
I re-ran with -K (e.g. guix pull -v3 --commit 2641621 -K 2>&1 | tee
guix-pull-bug-verbose-02) to keep build files, and a quick cat
/tmp/guix-build-util-linux-2.37.2.drv-0/util-linux-2.37.2/tests/output/misc/swaplabel.err
appears to confirm the bug
mkswap: error: swap area needs to be at least 10 pages
mkswap: <swapfile>: insecure permissions <perm>, fix with: chmod 0600
<swapfile>
mkswap: <swapfile> contains holes or other unsupported extents.
This swap file can be rejected by kernel on swap activation!
Use --verbose for more details.
mkswap: Label was truncated.
I'm still green to know how to fix this, but I presume if I check out the
latest version via git and the docs online, I should be able to update the
definition for util-linux to include the patch, then try again?
D
(name . Maxime Devos)(address . maximedevos@telenet.be)
CAJw6i1De5sx75mAfpiw_qNG8sz_0TUN-VH4htJgEWEb5n4ef5w@mail.gmail.com
On Thu, 3 Feb 2022 at 16:27, D. Birch <d.s.j.birch@gmail.com> wrote:
Toggle quote (21 lines)
>
> I re-ran with -K (e.g. guix pull -v3 --commit 2641621 -K 2>&1 | tee
> guix-pull-bug-verbose-02) to keep build files, and a quick cat
> /tmp/guix-build-util-linux-2.37.2.drv-0/util-linux-2.37.2/tests/output/misc/swaplabel.err
> appears to confirm the bug
>
> mkswap: error: swap area needs to be at least 10 pages
> mkswap: <swapfile>: insecure permissions <perm>, fix with: chmod 0600
> <swapfile>
>
> mkswap: <swapfile> contains holes or other unsupported extents.
> This swap file can be rejected by kernel on swap activation!
> Use --verbose for more details.
>
> mkswap: Label was truncated.
>
> I'm still green to know how to fix this, but I presume if I check out the
> latest version via git and the docs online, I should be able to update the
> definition for util-linux to include the patch, then try again?
>
> In fact, this was fixed upstream in commit
a02721f35b30d4ee0133446f016442f63117ddf6, is there a way I can easily
progress, by making use of that, or a later commit?
M
(name . D. Birch)(address . d.s.j.birch@gmail.com)
7d61641607e411b9e7e2c8cdff2d518418362840.camel@telenet.be
D. Birch schreef op do 03-02-2022 om 16:27 [+0000]:
Toggle quote (5 lines)
> I'm still green to know how to fix this, but I presume if I check out
> the latest version via git and the docs online, I should be able to
> update the definition for util-linux to include the patch, then try
> again?
There's no need for that, you can use the patch from Debian
and add it to the 'patches' field of 'util-linux'.
It's odd though that util-linux fails to build for you even
though https://bordeaux.guix..gnu.org has a substitute:
$ guix weather util-linux --system=aarch64-linux
Toggle quote (2 lines)
> [...]
Something else that's odd: there's only one hit for
$ grep -rF 'swap area needs to be at least ' | grep -F page
: the file tests/expected/misc/swaplabel.err. So how is mkswap
supposed to produce the message "mkswap: error: swap area needs to be
at least 10 pages' in the first place?
Greetings,
Maxime
?