[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1104037: golang-github-iovisor-gobpf: Add utsname support for riscv64 and loong64



On Thu, Apr 24, 2025 at 11:56:10PM +0800, Bo YU wrote:
> Source: golang-github-iovisor-gobpf
> Version: 0.2.0-9
> Severity: important
> Tags: patch
> User: debian-riscv@lists.debian.org
> Usertags: riscv64
> User: debian-loongarch@lists.debian.org 
> Usertags: loong64
> X-Debbugs-Cc: debian-riscv@lists.debian.org, debian-loongarch@lists.debian.org 
> 
> Dear Maintainer,

Hi Bo,

> now golang-github-iovisor-gobpf is missing utsname support for riscv64
> and loong64, this will lead to FTBFS from opensnitch on these
> architectures, see [0] and [1]. In fact this will also casuse the build
> to fail on these two architectures. Two PRs to support both architectures
> separately has been sent upstream, but has not yet been merged(inactive
> upstream), so I backport them to here. 

I see that your backport is not consistent with https://github.com/iovisor/gobpf/pull/316,
where the utsname for loong64 is of type int8. Any reason for this?

...

> 
> Could you apply this on next upload?

Give me a couple of more days so that the package migrates to testing.

I'd be glad to hear from the longarch porters whether to use int8 or uint8.

> -- 
> Regards,
> --
>   Bo YU

Thanks!
Dom

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05

Attachment: signature.asc
Description: PGP signature


Reply to: