Your message dated Tue, 7 Jan 2025 11:32:45 +0800
with message-id <[email protected]>
and subject line nix already build successed on loong64
has caused the Debian Bug report #1087607,
regarding nix: error "Missing support for fchmodat2"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1087607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087607
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nix
Version: 2.24.9+dfsg-2
Severity: normal
Tags: sid
User: [email protected]
Usertags: loong64

Dear maintainers,

Compiling the hardinfo failed for loong64 in the Debian Package Auto-Building environment.
The build error log is as follows,
```
conftest.c:35:13: error: #error "Missing support for fchmodat2"
   35 |           # error "Missing support for fchmodat2"
      |             ^~~~~
......
|           #include <seccomp.h>
|           #ifndef __SNR_fchmodat2
|           # error "Missing support for fchmodat2"
|           #endif
```

nix 2.18.1+dfsg-1 was built successfully on loong64 Buildds.
But after version 2.18.1+dfsg-1, there are 10 times failure.
The full log can be found at https://buildd.debian.org/status/fetch.php?pkg=nix&arch=loong64&ver=2.24.9%2Bdfsg-2&stamp=1731490304&raw=0.

After investigation, I found that fchmodat2 syscall is supported in libseccomp 2.5.5-2 version. Due to my local ENV's libseccomp  version is 2.5.5-2, So I provide some logs:
```
loongson@localhost:~/nix-2.24.9+dfsg$ grep "fchmodat2" -ri /usr/include/
/usr/include/seccomp-syscalls.h:#define __SNR_fchmodat2 __NR_fchmodat2
/usr/include/asm-generic/unistd.h:#define __NR_fchmodat2 452
/usr/include/asm-generic/unistd.h:__SYSCALL(__NR_fchmodat2, sys_fchmodat2)
/usr/include/loongarch64-linux-gnu/bits/syscall.h:#ifdef __NR_fchmodat2
/usr/include/loongarch64-linux-gnu/bits/syscall.h:# define SYS_fchmodat2 __NR_fchmodat2 loongson@localhost:~/nix-2.24.9+dfsg$ dpkg -S /usr/include/seccomp-syscalls.h
libseccomp-dev:loong64: /usr/include/seccomp-syscalls.h
loongson@localhost:~/nix-2.24.9+dfsg$ dpkg -l |grep libseccomp-dev
ii  libseccomp-dev:loong64                                 2.5.5-2
......
```
Now loong64's libseccomp version is 2.5.4-1 unreleased version(http://ftp.ports.debian.org/debian-ports/pool-loong64/main/libs/libseccomp/).

Please pay attention to the above phenomenon.

Best regards,
Dandan Zhang

--- End Message ---
--- Begin Message ---
Version: 2.24.9+dfsg-2

Hi,

nix already build successed on loong64, so close this bug.

https://buildd.debian.org/status/fetch.php?pkg=nix&arch=loong64&ver=2.24.9%2Bdfsg-2&stamp=1735323285&raw=0


-- 
肖盛文 xiao sheng wen -- Debian Developer(atzlinux)
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40debian.org
Debian salsa: https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB

Attachment: OpenPGP_0x00186602339240CB.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to