> On Sep 26, 2025, at 2:50 PM, Chris Sherlock <[email protected]> > wrote: > > Apologies to Ilmari, I seem to have replied to him directly a few times - > that was not my intention. > > A few points: > > I am running meson 1.9.1 via homebrew. > > However, I have checked compile_commands.json in the harfbuzz tarball build > and it is using: > > -D_LIBCPP_ENABLE_ASSERTIONS > > And not: > > -D_LIBCPP_HARDENING_MODE > > Unfortunately, I don’t know how to tweak the external tarball to use the > correct flag on macOS 26
I use LODE to build on macOS so I don’t know if this will help, but does setting the MESON environment variable work when you set it to the absolute path of your Homebrew meson like below when configuring?: MESON=/opt/homebrew/bin/meson ./autogen.sh Note: you can put "MESON=/opt/homebrew/bin/meson” in your autogen.input file instead of on the command line instead if you want. I tested this by doing a "make clean” in external/harfbuzz and external/meson folders and then rebuilt the whole source tree with make. I’ll do a “make distclean” and rebuild just to be safe. > > Furthermore, I checked the Gerrit change and I see that it uses: > > Darwin -a $MACOSX_SDK_VERSION > > When I run that on my terminal it complains that it can’t find Darwin. I’m > sure I’m missing something, but how does that check work? > I see the line in the configure script as the following. Maybe that is what you are referring to?: if test $_os = Darwin -a $MACOSX_SDK_VERSION -ge 260000; then $_os and $MACOSX_SDK_VERSION are initialized further up in the script and the if statement evaluates true for me in my macOS Tahoe build. > Chris >
smime.p7s
Description: S/MIME cryptographic signature
