Apple explicitly considers getentropy to not be a public API, and refuses to publish binaries to their App Store if you try to link against this API. This isn't so big of a deal, because I just pass ac_cv_func_getentropy=no to configure and go about my day... until 6cb0faf6ceec5b2e799e6fb5f04b85d135a7da9b, which for some reason has a one-off/haphazard check that //forces// a #define of HAVE_GETENTROPY and attempts to use a weak_import to proactively pull this forbidden symbol into my application :(. If configure determines this function isn't available, this function probably shouldn't be used, right? ;P This is forcing me to make a tactical retreat to an old version of gcrypt so I can publish my application.