Re: Input requested on proposed chnages for Delve compilation issues on ppc64le

[tshah <tshah@linux.ibm.com>]

Hello Alessandro,

I checked the file content of support_sentinel_linux.go, it doesnt 
contain the ppc64le tags but it still gives that error.

debian@ltc-zz14-lp9:~/delve/delve-1.24.0$ cat 
/home/debian/delve/delve-1.24.0/obj-powerpc64le-linux-gnu/src/github.com/go-delve/delve/pkg/proc/native/support_sentinel_linux.go
//go:build linux && !amd64 && !arm64 && !386 && !(riscv64 && 
exp.linuxriscv64)

// This file is used to detect build on unsupported GOOS/GOARCH 
combinations.

package your_linux_architecture_is_not_supported_by_delve
debian@ltc-zz14-lp9:~/delve/delve-1.24.0$


On 30/08/25 01:10, Alessandro Arzilli wrote:
> On Fri, Aug 29, 2025 at 03:39:59PM +0530, tshah wrote:
> > yeah, correct. I understand that exp.linuxppc64le was introduced as an
> > experimental build tag for |ppc64le.|I’ve looked into the suggestion of
> > removing the |!(ppc64le && exp.linuxppc64le)| clause from
> > |support_sentinel_linux.go|.
> >
> > That said, I’m trying to better understand the practical impact of removing
> > this clause. Additionally, even with this clause removed, I’m still
> > encountering the same build error on |ppc64le|.  Got the below error after
> > removing the clause. Is there any other place where the build tag might
> > still be enforced?
> >
> > src/github.com/go-delve/delve/service/debugger/debugger.go:31:2: found
> > packages native (dump_linux.go) and
> > your_linux_architecture_is_not_supported_by_delve
> > (support_sentinel_linux.go) in /home/debian/delve/delve-1.24.0/obj-powerpc64le-linux-gnu/src/github.com/go-delve/delve/pkg/proc/native
> No, I think you didn't remove it hard enough. Double check, have it cat somewhere the file that it's compiling, which would be:
>
> /home/debian/delve/delve-1.24.0/obj-powerpc64le-linux-gnu/src/github.com/go-delve/delve/pkg/proc/native/support_sentinel_linux.go