build: add loong64 arch support#8137
Merged
Merged
Conversation
Signed-off-by: 徐晓伟 <xuxiaowei@xuxiaowei.com.cn>
Signed-off-by: 徐晓伟 <xuxiaowei@xuxiaowei.com.cn>
696860e to
67f4b7c
Compare
yongtang
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
1. Why is this pull request needed and what does it do?
Add
loong64(LoongArch 64-bit) architecture support to CoreDNS build and release pipeline, enabling CoreDNS to run natively on LoongArch hardware.Changes:
Makefile.release: Addloong64toLINUX_ARCHfor release binary buildsMakefile.docker: Addloong64toLINUX_ARCHand configure Docker build args using community-providedghcr.io/loong64/debian:trixie-slimimages (follows the same pattern asriscv64which also uses non-official base images)2. Which issues (if any) are related?
#8136
3. Which documentation changes (if any) need to be made?
4. Does this introduce a backward incompatible change or deprecation?