Alan Third schrieb am Mo., 1. Jan. 2018 um 15:59 Uhr: > On Mon, Jan 01, 2018 at 01:15:09PM +0100, Philipp wrote: > > > > There are a few small bugs when building on macOS and not passing the > > right configure options. > > > > 1. When running configure without options, the build fails with an error > > > > xml.c:26:10: fatal error: 'libxml/tree.h' file not found > > #include > > ^~~~~~~~~~~~~~~ > > > > Apparently configure detects libxml2 to be present, but doesn't set the > > correct include path. > > This works fine here. Is it possible this was introduced by macOS > 10.13? > > Do you see the file in /usr/include/libxml2/libxml/? > No, /usr/include doesn't exist at all on my system. The include directory is /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include. > > > 2. When building with --without-libxml2, the build succeeds, but gives > > warnings like > > > > GEN ../../info/auth.info > > ./../emacs/docstyle.texi:3: warning: unrecognized encoding name `UTF-8'. > > > > This is because macOS ships an ancient version of makeinfo (4.8). It's > > possible to install a newer version using Homebrew, but that's not in > > PATH and therefore not found. Maybe configure could also search for > > makeinfo in the Homebrew directory (/usr/local/opt/texinfo/bin)? > > I’d think it’s the user’s responsibility to make sure /usr/local/bin > is on their path if they want to use homebrew stuff? > > /usr/local/bin doesn't contain makeinfo when installed via Homebrew. This is intentional; `brew info texinfo` says ==> *Caveats* This formula is keg-only, which means it was not symlinked into /usr/local, because software that uses TeX, such as lilypond and octave, require a newer version of these files. If you need to have this software first in your PATH run: echo 'export PATH="/usr/local/opt/texinfo/bin:$PATH"' >> ~/.bash_profile I can obviously do that or set MAKEINFO explicitly when invoking configure, but it would be nice if configure detected this situation automatically.