-
Notifications
You must be signed in to change notification settings - Fork 38
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
lftp does not build macOS 15 #1200
Comments
It's something related to libtool and enforcing symbol resolution (hardening the build). Those symbols actually do exist in other .o that should be linked in, or else the compiler should not be caring that they're not. Either libtool is being overly strict because it doesn't know that newer OS X do not require such strictness, or it's being appropriately strict and upstream doesn't know that it needs to make some adjustments. Try adding the following to PatchScript, which will reveal how libtool is calling the linker:
then look at the lines where proto-file.la is created. For me on 10.13, that is:
and there is no error. I bet for you the |
4.9.3 exploded worse for me, with a ton of duplicate-symbol errors and also a missing -std=c++17 flag (which would mean the this version of package needs to be dist-restricted). But either way, there is a compile-time flaw due to an ancient libtool. |
The line |
There are some duplicate symbol errors and a lot of extras. But this seems to be the first missing symbol definitions. I am building with maxbuildjobs=1 to avoid threading weirdness in the output.
Attaching the full output for the curious. I really can't see where this error originates. |
I get undefined symbols during linking. A lot of them. Tried updating to newer upstream 4.9.3 but get the same error.
I think the error is further up when the library is built where each of the object files has no symbols?
The text was updated successfully, but these errors were encountered: