From: Bo YU <firstname.lastname@example.org>
To: "Samuel Lid�n Borell" <email@example.com>
Subject: Re: cgit build on riscv64 machine
Date: Fri, 9 Sep 2022 10:29:21 +0800 [thread overview]
Message-ID: <20220909022921.yzgwbriypjiagl56@debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Tue, Jul 19, 2022 at 10:15:55AM +0200, Samuel Lid�n Borell wrote:
>On Tue, 19 Jul 2022 16:02:30 +0800, Bo YU <firstname.lastname@example.org> wrote:
>> >Are you using qemu-user?
>> It is interesting. In fact, I build it on real riscv64
>> hardware(Unmatched boards).
>> vimer@unmatched:~/build/07/31_cgit/cgit-master/tests$ uname -a
>> Linux unmatched 5.18.0-2-riscv64 #1 SMP Debian 5.18.5-1 (2022-06-16) riscv64 GNU/Linux
>> >That test uses strace, which in turn uses the ptrace() system call.
>> >qemu-user does not support ptrace(). At least it didn't when I tried a couple of years ago.
>> I just test strace cmd after see your hint, but it looks ok(If I do
>> wrong please conrect me)
>The strace output looks good to me. But did you check the strace.out file, that the test creates?
>The test will fail if it contains this string:
>Maybe something is causing that string to be printed.
Maybe I did not get your point, but now some people submit a patch:
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-09 2:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 2:44 Bo YU
2022-07-19 7:38 ` Samuel Lidén Borell
2022-07-19 8:02 ` Bo YU
2022-07-19 8:15 ` Samuel Lidén Borell
2022-07-19 8:46 ` Bo YU
2022-09-09 2:29 ` Bo YU [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).