-
Notifications
You must be signed in to change notification settings - Fork 20
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
configure does not work correctly on OS X #6
Comments
It's already using TMPDIR (TEMPDIR is derived from TMPDIR), would be good to trace the configure script to see where it's going wrong. But yeah, in general I don't think any of us tested on mac and it pretty much expects bash/gcc/gnu ld. There is an existing test for -lintl, but it's probably not picking up your custom package manager paths. |
I think this should fix some of these issues: |
yes, some of the errors are fixed now. -O1 is still an issue and libintl isn't getting linked in even though the configure script did find it:
|
Can you try again? |
Still doesn't link in libintl for me even though the configure script finds the library. Looks like -lintl isn't getting added to EXTRA_LDFLAGS:
I can get it to build if I modify the Makefile with:
|
Maybe 1dc158d fixes it, but if not please run:
And then paste the output of config.err here, that should be helpful in seeing what it's doing. |
Still doesn't link. config.err follows:
|
Whats the actual build failure output? Looks like bindtextdomain() is available without -lintl, so it must be one of the other functions used. |
Looks like github triggered on the commit text and autoclosed it despite the "may". :) |
The build failure output:
|
Hmm, I don't see why it works without -lintl during the configure test then. Maybe llvm is too smart and optimizes away the calls? |
We have another fix regarding In your case, this should automatically disable i18n and make the build pass. |
Tested on latest OS X and the configure script had many errors that caused it to fail. I eventually got it to work with the following changes:
ld: unknown option: -O1
The text was updated successfully, but these errors were encountered: