-
Notifications
You must be signed in to change notification settings - Fork 162
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
Linker issue on mipsel and armel architectures #515
Comments
@pgrt thanks for the report and apologies for the delay. This seems the kind of things that would be better done on a case-by-case basis, rather than hard-coding it in the build system. Could you try to see if you can manage to achieve the same effect by using environment variables instead? |
I mean something like |
Hello, No worry about the delay, really! Best, |
Hello again, Best, |
Great to hear, I'll close the issue report then. |
Hi @pgrt -- I recently got to the bottom of the same undefined __atomic_load_8 linking error in vcmi which, like pagmo, also uses libtbb. Maybe pagmo, which also is a CMake project experiences the same issue? I reported it here: uxlfoundation/oneTBB#1454 |
HI @josch and thanks for having me informed! I saw your report and the discussions that held afterwards. let's see if a solution can come from libtbb then; Best wishes, |
Hello,
In Debian, the build is failing on armel and mipsel with messages like
/usr/bin/ld: /usr/include/c++/11/bits/atomic_base.h:488: undefined reference to `__atomic_load_8'
I could solve this with the attached patch. Yet the issue is not showing up on other architectures: maybe you won't want to take it into account.
Best,
Pierre
linker_flags_for_armel_mipsel.txt
The text was updated successfully, but these errors were encountered: