Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

loongarch64 need glibc2.36

Open
  • Is something wrong?
#1,588 29 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, linux
Domain
operating-systems

Research direction

Start by reproducing the JNA 5.13 native-library failure on LoongArch under KylinOS v10 with glibc 2.28, then compare it with the reported ARM behavior. The issue provides no source file or test entry point, so identify which native artifact requires glibc 2.36 and confirm the compatibility result on both platforms.

Written by the indexing model from the issue text.

Description

with jna 5.13, i can use it in any linux platform with glibc2.28. but when i try to use loongarch platform with KylinOS v10 (glibc 2.28), it will tell me i need glibc2.36 but this system just support 2.28. In KylinOS v10 (glibc 2.28) for arm, i don't have this problem.

龙芯的 so 在银河麒麟v10 上跑的时候提示我 glibc 版本要求 2.36，但是银河麒麟用的是 2.28，这个是怎么适配的？没法用呀

Dominant language
Java
Stars
8.9k
Forks
1.7k
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from java-native-access/jna

All issues in java-native-access/jna

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.