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

gcc prefixes: Static linking LLVM may produce corrupt binaries #22743

Open
4 of 6 tasks
pal1000 opened this issue Dec 6, 2024 · 0 comments
Open
4 of 6 tasks

gcc prefixes: Static linking LLVM may produce corrupt binaries #22743

pal1000 opened this issue Dec 6, 2024 · 0 comments
Labels

Comments

@pal1000
Copy link
Contributor

pal1000 commented Dec 6, 2024

Description / Steps to reproduce the issue

This is known to reproduce with mingw-w64-mesa at least:

  1. Change -Dsshared-llvm to disabled in mingw-w64-mesa/PKGBUILD;
  2. Build with makepkg-mingw as usual.

Expected behavior

Build should succeed or produce no extra errors and warnings compared to when LLVM is dynamically linked.

Actual behavior

Build succeeds in theory but there are linker complaints.
Resulting binaries are corrupt and unusable.

mesa-dist-win build script log

mesa-llvm-static-gcc.txt

makepkg-mingw should reproduce it too except for MINGW32 prefix as it has LLVM support disabled in PKGBUILD.

Verification

Windows Version

MINGW64_NT-10.0-20348

MINGW environments affected

  • MINGW64
  • MINGW32
  • UCRT64
  • CLANG64
  • CLANGARM64

Are you willing to submit a PR?

This far exceeds my programing skill.

@pal1000 pal1000 added the bug label Dec 6, 2024
pal1000 added a commit to pal1000/MINGW-packages that referenced this issue Dec 6, 2024
pal1000 added a commit to pal1000/MINGW-packages that referenced this issue Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant