this is already merged in main

OTOH the official Go name is loong64. Hmm.

It doesn't matter, really. Say GOARCH is amd64 while seccomp's name is x86_64.

IOW, this library should support the same names as libseccomp.

OTOH the official Go name is loong64. Hmm.

It doesn't matter, really. Say GOARCH is amd64 while seccomp's name is x86_64.

As you said, GOARCH is amd64, and the name of seccomp is x86_64, so in libseccomp-golang/seccomp.go(https://github.com/seccomp/libseccomp-golang/blob/main/seccomp.go), the case branch adds x86_64 and amd64 to solve the name inconsistency problem:

`
switch strings.ToLower(arch) {
case "x86":
return ArchX86, nil
case "amd64", "x86-64", "x86_64", "x64":
return ArchAMD64, nil

`

For LoongArch, GOARCH is loong64 and seccomp is loongarch64. Similarly, we should include loong64 and loongarch64 in the case branch to solve the name inconsistency problem, runc is a good example, and this problem has blocked the runc test build upstream of debian.

this is already merged in main

Currently only loongarch64 is included, loong64 is missing:
case "loongarch64": return ArchLOONGARCH64, nil

For this problem, the relevant patch has been merged into Debian in advance(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095452).

@kolyshkin
Hi, is there any latest progress on this issue?

@kolyshkin
Hi, I still hope that this problem can be fixed here, not just in the Debian upstream community.
The code for fixing it in Debian upstream is as follows:

 const (
@@ -306,6 +308,8 @@ func GetArchFromString(arch string) (Scm
 		return ArchPARISC64, nil
 	case "riscv64":
 		return ArchRISCV64, nil
+	case "loongarch64", "loong64":
+		return ArchLOONGARCH64, nil
 	default:
 		return ArchInvalid, fmt.Errorf("cannot convert unrecognized string %q", arch)
 	}

Detailed patch link address:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1095322;filename=golang-github-seccomp-libseccomp-golang-add-loongarch64-support.patch;msg=5

@zhaixiaojuan please sign your commit.

Yes, I think GetArchFromString can and should recognize GOARCH values.

We'll release v0.11.1 once this is merged.