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
LDFLAGS containing "-Wl,-z,pack-relative-relocs" breaks build #24919
Comments
+1, currently am using sed to remove the offending flag but it would be nice not to have to do this. |
You don't need to call
|
That works too - I guess sed is a little heavy. I did not realize echo could do that...and I've been using Linux for like 20 years. |
Yep, power stuff, see: https://www.cyberciti.biz/tips/bash-shell-parameter-substitution-2.html |
Not sure what's going on, but if you build with CMake command
Output
|
Thanks for the suggestion, will give it a try... what does |
With this the Mold linker is used. Requires Mold to be installed though. So far I don't understand why it makes a difference but it somehow works? |
Bug report
Describe the bug
Here is a clear and concise description of what the problem is:
When building with LDFLAGS containing
-Wl,-z,pack-relative-relocs
, cmake fails to find Threads.Expected Behavior
Here is a clear and concise description of what was expected to happen:
The build should work.
Actual Behavior
The build breaks:
Possible Fix
To Reproduce
Steps to reproduce the behavior:
Note: these are currently Arch Linux's distro default:
Debuglog
The debuglog can be found here:
Screenshots
Here are some links or screenshots to help explain the problem:
Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:
Your Environment
Used Operating system:
Android
iOS
tvOS
Linux
macOS
Windows
Windows UWP
Operating system version/name: Arch Linux
Kodi version: master
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered: