Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No symbol version section for memcpy@GLIBC_2.2.5 on linux ARM64 #8

Closed
sorumehta opened this issue Feb 7, 2024 · 3 comments
Closed

Comments

@sorumehta
Copy link
Contributor

I am running linux (fedora) on arm64 architecture (apple silicon). When I run make inside glfw/lib, after compilation I get the following error during linking step:

no symbol version section for versioned symbol memcpy@GLIBC_2.2.5

I do want to fix this and create a PR, but I am not really sure where to begin.
One thing I noticed that in the directory glfw/lib/glibcver there are platform specific files like glibc_2.9_x64.h, but no corresponding glibc file for arm64. Can this be one of the causes?

Thanks.

@Shinmera
Copy link
Member

Shinmera commented Feb 7, 2024

Yeah, I forgot about that header. Sorry about that. Let me see if I can find a replacement...

@Shinmera
Copy link
Member

Shinmera commented Feb 7, 2024

Okey, looks like wheybags/glibc_version_header#35 is outstanding for now. I've just disabled static glibc version linking for now on ARM64, which means the produced binary will be tied to the host's GLIBC version number (and thus not be backwards compatible), but at least the compilation should succeed now.

sorumehta added a commit to sorumehta/glfw that referenced this issue Feb 7, 2024
@sorumehta
Copy link
Contributor Author

@Shinmera Thank you! I am able to build it now, and raised a PR. But I am not sure how would the new file be located by cffi? Does it need to have a particular naming pattern?

Shinmera pushed a commit that referenced this issue Feb 7, 2024
* include linux arm64 static file, fixes issue #8
@Shinmera Shinmera closed this as completed Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants