Skip to content
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

Fix Autoconf checks on Darwin #2196

Closed
wants to merge 1 commit into from
Closed

Conversation

danchr
Copy link

@danchr danchr commented Oct 21, 2020

The Autoconf checks merely verify that the symbol is available and linkable, but not that it's actually defined and usable. This breaks compilation on recent versions of macOS, where lgamma_r() is unavailable unless _REENTRANT is defined. Since this is rather difficult to detect, I strengthened the check so that it simply omits lgamma_r on macOS.

While at it, I added support for exp10() on macOS, which is available, but named __exp10 due to its nonstandard nature.

The Autoconf checks merely verify that the symbol is available and
linkable, but not that it's actually defined and usable. This breaks
compilation on recent versions of macOS, where `lgamma_r()` is
unavailable unless `_REENTRANT` is defined. Since this is rather
difficult to detect, I strengthened the check so that it simple omits
lgamma_r on macOS.

While at it, I added support for `exp10()` on macOS, which is
available, but named `__exp10` due to its nonstandard nature.
@coveralls
Copy link

coveralls commented Oct 21, 2020

Coverage Status

Coverage increased (+0.03%) to 84.16% when pulling 8e1a4c0 on danchr:autoconf-darwin into a17dd32 on stedolan:master.

@wtlangford
Copy link
Contributor

I ended up resolving this as part of a larger set of autoconf improvements in 77417c1 and e660003, but thanks for the contribution!

@wtlangford wtlangford closed this May 1, 2021
@danchr danchr deleted the autoconf-darwin branch May 4, 2021 13:13
@dave-r12
Copy link

dave-r12 commented Nov 6, 2022

Hey, I also ran into this when attempting to build from the 1.6 release. Would you have a recommendation for how to resolve it for that? Also worth noting -- when I build it with homebrew I don't run into this issue. I'm inexperienced building things from source, so am a bit confused how homebrew doesn't seem to run into this for the 1.6 release. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants