-
Notifications
You must be signed in to change notification settings - Fork 626
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
slint-lsp _ZN7QObject10timerEventEP11QTimerEvent: /usr/lib/libQt6Core.so.6: error due to GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS #7174
Comments
|
yes
|
Faced the same issue
|
It seems the problem only related to Arch users (or arch-based distros) Plasma launcher had the same issue Thanks to comment of @Scrumplex, the problem in the commit in Arch repo of qt6-base So to fix the problem you can build qt6-base from source
After this steps |
Another way to solve this issue is install slint-lsp using
and then prepend It is more simple and do not break system Qt package. I'm using neovim for developing slint app now, I configured
VSCode or other IDEs may have similar options. |
Searching for the error on google returns https://bugreports.qt.io/browse/QTBUG-115261 |
Don't link against Qt in our binary because it might not be binary compatible with all distributions. Eg, archlinux shows this error: `error due to GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS` We also don't enable the Qt backend in our vscode extension Fixes #7174
Don't link against Qt in our binary because it might not be binary compatible with all distributions. Eg, archlinux shows this error: `error due to GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS` We also don't enable the Qt backend in our vscode extension Fixes #7174
Don't link against Qt in our binary because it might not be binary compatible with all distributions. Eg, archlinux shows this error: `error due to GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS` We also don't enable the Qt backend in our vscode extension Fixes #7174
Bug Description
error when run slint-lsp v1.9.0 on linux
Reproducible Code (if applicable)
No response
Environment Details
Product Impact
No response
The text was updated successfully, but these errors were encountered: