From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
YOANN P <yoann_mac_donald@hotmail.com>
Subject: Re: Include Proot-static with binary releases
Date: Sat, 23 Mar 2019 17:53:42 +0100 [thread overview]
Message-ID: <20190323175342.7a238f95@scratchpost.org> (raw)
In-Reply-To: <87vafs4oll.fsf@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
On Tue, 23 Jan 2018 15:49:26 +0100
ludovic.courtes@inria.fr (Ludovic Courtès) wrote:
> > Currently proot only build successfully on x86_64 and i686, so that is
> > something we would need to fix first.
Are you sure that is not just a limitation of the qemu transparent emulation?
I examined the test failures in proot-static and it's clear that qemu will have
some trouble finding out what one wants to happen:
>#include <unistd.h> /* execve(2), */
>#include <stdlib.h> /* exit(3), */
>#include <string.h> /* strcmp(3), */
>
>int main(int argc, char *argv[])
>{
> if (argc == 0)
> exit(EXIT_SUCCESS);
>
> execve("/proc/self/exe", NULL, NULL);
> exit(EXIT_FAILURE);
>}
Now, qemu transparent emulation still picks up, but then the missing
argv[0] will be a problem.
And indeed,
$ guix environment -s armhf-linux proot-static
[...]
[env]$ ./test-25069c12
qemu: no user program specified
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-23 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 21:52 Include Proot-static with binary releases YOANN P
2018-01-18 10:44 ` Ludovic Courtès
2018-01-18 14:21 ` Pjotr Prins
2018-01-22 17:45 ` Efraim Flashner
2018-01-23 14:49 ` Ludovic Courtès
2019-03-23 16:53 ` Danny Milosavljevic [this message]
2019-03-25 9:16 ` Ludovic Courtès
2018-01-21 14:50 ` Ricardo Wurmus
2018-01-21 21:03 ` Pjotr Prins
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190323175342.7a238f95@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=yoann_mac_donald@hotmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.