-
Notifications
You must be signed in to change notification settings - Fork 37
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
Build failure on Mac OS X 10.13.2 (Unable to specify soname (is Darwin supported?)) #181
Comments
Which one is it? :p I somehow suspect making required flags unrequired isn't the solution though. |
Have you tried the Meson build? |
Which compiler are you using, anyway, that doesn't support -Wl,--no-undefined and doesn't support Darwin's -install_name |
Lol sorry I can see that's ambiguous now, it was late. Running the script produces no visible errors, most of the printed checks pass and there's no indication that it did not succeed.
But, as mentioned, it doesn't produce the necessary files in
I don't suspect that either, but I figured that my environment is supposed to be sufficient for
The script asks for
I also tried
I just tried it (after installing If it's useful, here's the output of Meson:
|
This hasn’t moved for a while. To go further, here’s what both
and here’s
So the culprit linker options are never actually called, because |
It is to be expected that meson works -- meson internally knows how to handle such options as Seems like the handwritten configure script could be updated to support Darwin better though... I know little to nothing about that toolchain, but:
|
Hi,
Running
./configure
works with no errors at first, but runningmake
afterwards yields:(and indeed
.build
only containscheck.c
)So I went searching in the
configure
script for what's going wrong --We never make it past line 204:
test_ldflags
goes through with argument-fPIC
, but the next argument,-Wl,--no-undefined
fails and the script exits (I'm not entirely sure if the arguments are being passed correctly to the function, but this is what's being passed).So I removed the line that causes the script to exit on failure, 178:
And now I get stuck at this error:
Do you have any idea of what's going wrong? Thanks
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin17)
but I also tried to
sh
itThe text was updated successfully, but these errors were encountered: