[tz] Errors compiling 2022f on macOS
Gilmore Davidson
gilmoreorless at gmail.com
Sun Oct 30 22:28:30 UTC 2022
On 31 Oct 2022, at 04:40, Paul Eggert <eggert at cs.ucla.edu> wrote:
>
> it appears that it's common for a macOS build host to have misconfigured copies of arm64 and x86_64 libraries - possibly because migration assistance copied over an old homebrew system, and possibly with different versions on x86_64 vs arm64 - and where <libintl.h> therefore compiles (because the same libintl.h works for multiple architectures and versions) but the resulting program doesn't link. My guess is that Gilmore has such a system and this broke zic linking
That wouldn’t surprise me in the least. My current system has accumulated many years of possible junk via upgrades.
>
> If you think the attached patch is headed in the wrong direction, I'll revert it and instead ask users like Gilmore with messed-up build hosts to build with 'make CFLAGS="-DHAVE_GETTEXT=0"', which they already have to do with 2022f
That patch worked for me. I can now run `make` with no arguments and no errors. But I’m also fine with running the flags if the patch is reverted.
More information about the tz
mailing list