-
Notifications
You must be signed in to change notification settings - Fork 333
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 problem: file was built for archive which is not the architecture being linked #11
Comments
You must use the correct
Otherwises it uses the system |
Thanks! That fixes the problem. I should have thought about that... And thank you for this great project! |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a problem with the linker, which i was unable to resolve in the last days. It might be a bug within the linker or my configuration, but i am stuck and digging in the linker source code is the least favorite thing i'd like to do...
At first: The same test works on OSX when using clang++ instead of o64-clang++
Building the library is fine. Compiling and linking the example fails with the following errors:
I have used ranlib on the library. I have checked the architecture with otool/lipo and everything looks just right. It is definitly X86_64.
You can use this small test to verify the problem. (Same happens if you statically compile Boost and then want to link to it)
Any hints would be really appreciated.
Michael
The text was updated successfully, but these errors were encountered: