chai2010 / chai2010/webp

arm64 build error

Open
#59 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
723
Forks
113
PR merge metrics
No merged PRs in 30d

Description

Getting Build errors when I try to build my project for arm64

CGO_ENABLED is enabled. The Build Command:

`env GOOS=linux GOARCH=arm64 go build -o build/app-arm64`

The Error:

`$ env GOOS=linux GOARCH=arm64 go build -o build/app-arm64
90# runtime/cgo
91gcc_arm64.S: Assembler messages:
92gcc_arm64.S:30: Error: no such instruction: stp x29,x30,[sp,'
93gcc_arm64.S:34: Error: too many memory references for `mov'
94gcc_arm64.S:36: Error: no such instruction: stp x19,x20,[sp,'
95gcc_arm64.S:39: Error: no such instruction: stp x21,x22,[sp,'
96gcc_arm64.S:42: Error: no such instruction: stp x23,x24,[sp,'
97gcc_arm64.S:45: Error: no such instruction: stp x25,x26,[sp,'
98gcc_arm64.S:48: Error: no such instruction: stp x27,x28,[sp,'
99gcc_arm64.S:52: Error: too many memory references for mov'
100gcc_arm64.S:53: Error: too many memory references for mov'
101gcc_arm64.S:54: Error: too many memory references for mov'
102gcc_arm64.S:56: Error: no such instruction: blr x20'
103gcc_arm64.S:57: Error: no such instruction: blr x19'
104gcc_arm64.S:59: Error: no such instruction: ldp x27,x28,[sp,'
105gcc_arm64.S:62: Error: no such instruction: ldp x25,x26,[sp,'
106gcc_arm64.S:65: Error: no such instruction: ldp x23,x24,[sp,'
107gcc_arm64.S:68: Error: no such instruction: ldp x21,x22,[sp,'
108gcc_arm64.S:71: Error: no such instruction: ldp x19,x20,[sp,'
109gcc_arm64.S:74: Error: no such instruction: ldp x29,x30,[sp],'`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported command, `env GOOS=linux GOARCH=arm64 go build -o build/app-arm64`, with CGO enabled and inspect the assembler errors from `runtime/cgo`. Determine whether the ARM64 cross-compilation toolchain is configured correctly; done means the project builds successfully for Linux ARM64 without these errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.