From: 王洪亮 <wanghongliang@loongson.cn>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: add loongarch64 port
Date: Wed, 27 Apr 2022 09:58:44 +0800 [thread overview]
Message-ID: <39446a33-e5df-8912-e39d-308101275e8a@loongson.cn> (raw)
In-Reply-To: <CAK8P3a1d=jHPn0CdNYROWffoyxBhj3cmXJpO_Sb10T39zFS+wg@mail.gmail.com>
在 2022/3/31 下午4:14, Arnd Bergmann 写道:
> The __NR_fstat and __NR_newfstatat symbols are only defined by
> the kernel if __ARCH_WANT_NEW_STAT is set, which should not be
> by the time the kernel port is merged. Instead, user space should
> call statx() here, which continues to be supported as a superset.
>
>
> Arnd
there is a build error if I remove __NR_fstat and __NR_newfstatat,
the architecture-independent code depends on the __NR_fstat and
__NR_fstatat defined in architecture platform.
How to deal with this issue?
In file included from src/stat/fstatat.c:8:
src/stat/fstatat.c: In function ‘fstatat_kstat’:
src/stat/fstatat.c:78:19: error: ‘SYS_fstat’ undeclared (first use in
this function); did you mean ‘SYS_statx’?
ret = __syscall(SYS_fstat, fd, &kst);
src/stat/fstatat.c:80:20: error: ‘SYS_fstatat’ undeclared (first use in
this function); did you mean ‘SYS_fstatfs’?
ret = __syscall(SYS_fstatat, fd, path, &kst, flag);
Hongliang Wang
next prev parent reply other threads:[~2022-04-27 1:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 6:20 王洪亮
2022-03-31 8:14 ` Arnd Bergmann
2022-04-01 7:40 ` 王洪亮
2022-04-01 7:48 ` Arnd Bergmann
2022-04-02 6:19 ` 王洪亮
2022-04-02 7:21 ` Rich Felker
2022-04-02 9:53 ` 王洪亮
2022-04-27 1:58 ` 王洪亮 [this message]
2022-04-27 2:13 ` Rich Felker
2022-03-31 18:47 ` Rich Felker
2022-04-02 7:59 ` 王洪亮
2022-04-06 2:08 ` 王洪亮
2022-04-06 16:00 ` Markus Wichmann
2022-04-08 2:21 ` 王洪亮
2022-04-08 6:46 ` Arnd Bergmann
2022-04-09 3:54 ` 王洪亮
2022-04-09 11:06 ` Arnd Bergmann
2022-04-09 13:19 ` Rich Felker
2022-04-09 13:30 ` Rich Felker
2022-04-10 10:30 ` Arnd Bergmann
2022-04-10 15:26 ` Rich Felker
2022-04-11 8:03 ` Arnd Bergmann
2022-04-11 12:11 ` Rich Felker
2022-04-11 13:01 ` Arnd Bergmann
2022-04-12 1:11 ` 王洪亮
2022-04-13 1:16 ` 王洪亮
2022-04-13 7:26 ` Christian Brauner
2022-04-13 8:26 ` Arnd Bergmann
2022-04-13 9:04 ` Christian Brauner
2022-04-13 13:25 ` Arnd Bergmann
2022-04-13 14:09 ` Rich Felker
2022-04-14 9:36 ` Christian Brauner
2022-04-20 9:09 ` 王洪亮
2022-04-20 13:33 ` Christian Brauner
2022-04-20 13:54 ` Rich Felker
2022-04-21 6:54 ` 王洪亮
2022-04-14 9:36 ` Christian Brauner
2022-04-13 7:19 ` Christian Brauner
2022-04-13 14:06 ` Rich Felker
2022-04-11 3:40 ` 王洪亮
-- strict thread matches above, loose matches on Subject: below --
2022-03-22 3:52 [musl] " 王洪亮
2022-03-29 8:12 ` [musl] " 王洪亮
2022-03-29 8:26 ` Arnd Bergmann
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=39446a33-e5df-8912-e39d-308101275e8a@loongson.cn \
--to=wanghongliang@loongson.cn \
--cc=musl@lists.openwall.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 public inbox
https://git.vuxu.org/mirror/musl/
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).