From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix@gnu.org
Subject: Re: Issues building some packages with QEMU binfmt
Date: Mon, 09 Mar 2020 23:00:17 +0100 [thread overview]
Message-ID: <87y2s9chou.fsf@GlaDOS.home> (raw)
In-Reply-To: <87ftemeblt.fsf@cbaines.net> (Christopher Baines's message of "Thu, 05 Mar 2020 21:27:26 +0000")
Hi Chris,
Christopher Baines <mail@cbaines.net> writes:
> Hey,
>
> For the Guix Data Service, I've noticed some builds getting stuck
> recently. It seems to be when qemu-arm is used to run foreign binaries,
> often grep during the git-minimal tests. Currently it's stuck running
> gcc during the configure phase for the Guix package.
>
> Attaching strace to the stuck process shows the following output in a
> loop, mmap followed by munmap:
>
> mmap(0xab897cd96000, 4294901760, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x7ffef0010000
> mmap(0x7ffff0000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffff70c1000
> munmap(0x7ffff70c1000, 4096) = 0
> munmap(0x7ffef0010000, 4294901760) = 0
>
>
> I'm guessing this is probably an issue with QEMU, but I was wondering if
> anyone has seen similar behaviour?
I've experienced the exact same thing: Some months ago I attempted to
build the Guix package for armhf-linux on my x86_64-linux machine
(because there were no substitutes) using the qemu-binfmt service. I
eventually gave up because it always got stuck (I tried it several
times). In fact I tried it again today and it got stuck during the
`build' phase running sed.
Regards,
Diego
prev parent reply other threads:[~2020-03-09 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 21:27 Issues building some packages with QEMU binfmt Christopher Baines
2020-03-09 22:00 ` Diego Nicola Barbato [this message]
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=87y2s9chou.fsf@GlaDOS.home \
--to=dnbarbato@posteo.de \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.net \
/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).