From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=MAILING_LIST_MULTI, NICE_REPLY_A,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31182 invoked from network); 27 Apr 2022 01:59:03 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 27 Apr 2022 01:59:03 -0000 Received: (qmail 13625 invoked by uid 550); 27 Apr 2022 01:58:59 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 13584 invoked from network); 27 Apr 2022 01:58:58 -0000 To: musl@lists.openwall.com References: <64c0ef49-4618-8eca-c826-bd2a840c284b@loongson.cn> From: =?UTF-8?B?546L5rSq5Lqu?= Message-ID: <39446a33-e5df-8912-e39d-308101275e8a@loongson.cn> Date: Wed, 27 Apr 2022 09:58:44 +0800 User-Agent: Mozilla/5.0 (X11; Linux mips64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CM-TRANSID:AQAAf9AxisxUo2hiuPUyAA--.1319S3 X-Coremail-Antispam: 1UD129KBjvdXoW7Gr15tr13tFWxGr4Dtr4fXwb_yoWDCrXEgr W7t39IkFyxJrnrKF9xWFsxJFWxCrW8Kr9rZaykXryakw4UtFWUWr4fWw45GF1DWF45trWk uF1ayF95Cr9xtjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbIxYjsxI4VWxJwAYFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVW5JVW7JwA2z4x0Y4vE2Ix0 cI8IcVCY1x0267AKxVWxJVW8Jr1l84ACjcxK6I8E87Iv67AKxVW8Jr0_Cr1UM28EF7xvwV C2z280aVCY1x0267AKxVW8Jr0_Cr1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAC Y4xI64kE6c02F40Ex7xfMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJV W8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IY64vIr41lc7I2V7IY0VAS07AlzVAYIcxG 8wCY02Avz4vE-syl42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxV Aqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1j 6r15MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6x kF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE 14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa 7IU86OJ5UUUUU== X-CM-SenderInfo: pzdqwxxrqjzxhdqjqz5rrqw2lrqou0/ Subject: Re: [musl] Re: add loongarch64 port 在 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