-
Notifications
You must be signed in to change notification settings - Fork 166
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
Error when building for MacCatalyst: ld: symbol(s) not found for architecture x86_64 #447
Comments
It's normal that there are errors in For the |
Unfortunately, deleting all object files did not help. I deleted all the object files inside this path (there is a folder also which is defined as my |
I ran my script on a Mac Catalina with lower OS versions, but I get the same error. Should I also delete such files from my |
I found the issue, it was a silly one. Target and build were swapped. |
Okay, I can't really confirm that this issue was resolved because I couldn't generate the library (output was only a |
As it turns out, target and build were not swapped.
which is correct (I guess). The initial issue isn't fixed yet. The output was a .la file because my build script didn't run |
@yoKurt94 |
It is not solved yet, but I am still working on it. I could of course give you what I have so far.
… Am 22.03.2022 um 03:22 schrieb JzwOnly ***@***.***>:
@yoKurt94
Is this problem solved? Can you share the script for compiling Mac Catalyst?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
I try to build freeTDS for MacCatalyst but I am getting an error in my terminal saying:
ld: building for macOS, but linking in object file built for Mac Catalyst, file '.libs/ct.o' for architecture x86_64
I cannot explain how this can be since my configure does not seem to build for MacOS:
I noticed in my
config.log
that there are some ld errors:What is the issue with these symbols? I feel like my configure should be set up correctly.
config.log
The text was updated successfully, but these errors were encountered: