Skip to content

Conversation

wszqkzqk
Copy link
Contributor

LoongArch is a new RISC ISA developed by loongson. There are already a lot of community support and testing about it.

I've added support of loong64 upstream in conda/rattler#1534 so we may take it forward now.

Signed-off-by: Zhou Qiankang <[email protected]>
@wszqkzqk wszqkzqk marked this pull request as draft July 18, 2025 12:12
@lucascolley lucascolley changed the title fix: support for loong64 linux feat: support for loong64 linux Jul 21, 2025
@lucascolley lucascolley added the enhancement New features label Jul 21, 2025
@ruben-arts
Copy link
Contributor

Updated the branch, as we now have a new version of rattler that supports this.

@wszqkzqk wszqkzqk marked this pull request as ready for review July 25, 2025 12:25
wszqkzqk added a commit to lcpu-club/loongarch-packages that referenced this pull request Jul 26, 2025
* Backport loong64 support in rattler:
conda/rattler@e9152cd
* Backport loong64 support in pixi:
prefix-dev/pixi#4163
* Add our trampoline binary
* Skip failed tests caused by lack of wheel packages upstream

Signed-off-by: Zhou Qiankang <[email protected]>
@wszqkzqk
Copy link
Contributor Author

Updated the branch, as we now have a new version of rattler that supports this.

It has been successfully built on Arch Linux for Loong64 now with this PR applied and the trampoline binary manually downloaded.

@lucascolley lucascolley merged commit 7912ca6 into prefix-dev:main Jul 31, 2025
83 of 84 checks passed
@lucascolley
Copy link
Collaborator

thanks all!

@lucascolley
Copy link
Collaborator

CI failed on main after merging this:

  # Set the repository to push to the repository the workflow is running on
  git config user.name "GitHub Actions"
  git config user.email "[email protected]"
  git add trampoline/binaries/
  git commit -m "[CI]: Update trampoline binaries for all targets"
  # Push changes to the branch that triggered the workflow
  BRANCH=${GITHUB_REF#refs/heads/}
  git push origin HEAD:$BRANCH
  shell: /usr/bin/bash -e {0}
[main ed143e5] [CI]: Update trampoline binaries for all targets
 9 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 trampoline/binaries/pixi-trampoline-loongarch64-unknown-linux-gnu.zst
remote: error: GH006: Protected branch update failed for refs/heads/main.        
remote: 
remote: - Changes must be made through a pull request.        
remote: 
remote: - 7 of 7 required status checks are expected.        
To https://github.com/prefix-dev/pixi
 ! [remote rejected] HEAD -> main (protected branch hook declined)
error: failed to push some refs to 'https://github.com/prefix-dev/pixi'

@wszqkzqk
Copy link
Contributor Author

wszqkzqk commented Aug 2, 2025

CI failed on main after merging this:

  # Set the repository to push to the repository the workflow is running on
  git config user.name "GitHub Actions"
  git config user.email "[email protected]"
  git add trampoline/binaries/
  git commit -m "[CI]: Update trampoline binaries for all targets"
  # Push changes to the branch that triggered the workflow
  BRANCH=${GITHUB_REF#refs/heads/}
  git push origin HEAD:$BRANCH
  shell: /usr/bin/bash -e {0}
[main ed143e5] [CI]: Update trampoline binaries for all targets
 9 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 trampoline/binaries/pixi-trampoline-loongarch64-unknown-linux-gnu.zst
remote: error: GH006: Protected branch update failed for refs/heads/main.        
remote: 
remote: - Changes must be made through a pull request.        
remote: 
remote: - 7 of 7 required status checks are expected.        
To https://github.com/prefix-dev/pixi
 ! [remote rejected] HEAD -> main (protected branch hook declined)
error: failed to push some refs to 'https://github.com/prefix-dev/pixi'

So what should we do? Add the trampoline binary manually?

@wszqkzqk
Copy link
Contributor Author

Does the trampoline binary file need to be updated by the bot?

@baszalmstra
Copy link
Contributor

@nichmor did you do this manually last time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants