From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Kars de Jong <jongk@linux-m68k.org>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k: Wire up clone3() syscall
Date: Sun, 15 Dec 2019 18:01:42 +0100 [thread overview]
Message-ID: <009ee46a-eb51-f76f-915d-baa883f0be24@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdVLQF_KyWDn=HxmLAp6Vy3jyw=JLDQWryLt809sCecosA@mail.gmail.com>
On 12/15/19 5:48 PM, Geert Uytterhoeven wrote:
> With Ubuntu's libc6-m68k-cross installed, the selftest binaries cross-build
> fine. Running them on a very old Debian requires some hackery:
>
> 1. Copy ld.so.1, ld-2.27.so, libc.so.6, and libc-2.27.so from
> /usr/m68k-linux-gnu/lib/ to /tmp/lib on the m68k target,
> 2. mkdir /tmp/proc && mount proc /tmp/proc -t proc,
> 3. chroot /tmp /tmp/<test-binary>.
Why not use a recent environment?
> https://wiki.debian.org/M68k/QemuSystemM68k
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2019-12-15 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 19:52 [PATCH] m68k: Wire up clone3() syscall Kars de Jong
2019-11-25 9:12 ` Geert Uytterhoeven
2019-11-26 14:41 ` Christian Brauner
2019-11-26 15:29 ` Kars de Jong
2019-12-15 16:48 ` Geert Uytterhoeven
2019-12-15 17:01 ` John Paul Adrian Glaubitz [this message]
2019-12-15 20:06 ` Geert Uytterhoeven
2019-12-16 10:31 ` Christian Brauner
2019-12-18 9:57 ` Kars de Jong
2020-01-12 16:06 ` Geert Uytterhoeven
2020-01-13 9:10 ` Geert Uytterhoeven
2020-01-13 9:18 ` Christian Brauner
2020-01-13 9:34 ` Geert Uytterhoeven
2020-01-13 10:17 ` Christian Brauner
2020-01-13 10:31 ` Geert Uytterhoeven
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=009ee46a-eb51-f76f-915d-baa883f0be24@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=christian.brauner@ubuntu.com \
--cc=geert@linux-m68k.org \
--cc=jongk@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
/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 NNTP newsgroup(s).