From: Philipp Stephani <p.stephani2@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 29931@debbugs.gnu.org
Subject: bug#29931: 27.0.50; Slightly suboptimal build behavior on macOS
Date: Mon, 01 Jan 2018 15:05:02 +0000 [thread overview]
Message-ID: <CAArVCkQB8wzNEQPu4tZv9Ycacm8AHZLsMAtYQREWNiHP3G+Kcg@mail.gmail.com> (raw)
In-Reply-To: <20180101145919.GC86834@breton.holly.idiocy.org>
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]
Alan Third <alan@idiocy.org> 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 <libxml/tree.h>
> > ^~~~~~~~~~~~~~~
> >
> > 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.
[-- Attachment #2: Type: text/html, Size: 3414 bytes --]
next prev parent reply other threads:[~2018-01-01 15:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 12:15 bug#29931: 27.0.50; Slightly suboptimal build behavior on macOS Philipp
2018-01-01 13:13 ` Noam Postavsky
2018-01-01 13:51 ` Philipp Stephani
2018-01-01 14:54 ` Alan Third
2018-01-01 14:59 ` Alan Third
2018-01-01 15:05 ` Philipp Stephani [this message]
2018-01-01 15:12 ` Philipp Stephani
2018-01-01 15:53 ` Alan Third
2018-01-02 12:10 ` Alan Third
2018-01-02 20:03 ` Philipp Stephani
2018-01-02 21:51 ` Alan Third
2018-01-02 19:51 ` Philipp Stephani
2018-01-01 15:48 ` Alan Third
2018-01-02 19:42 ` Philipp Stephani
2018-01-02 19:48 ` Philipp Stephani
2018-01-02 19:49 ` Philipp Stephani
2018-01-02 20:04 ` Eli Zaretskii
2018-01-02 20:19 ` Alan Third
2018-01-02 21:24 ` Alan Third
2018-01-07 14:05 ` Philipp Stephani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArVCkQB8wzNEQPu4tZv9Ycacm8AHZLsMAtYQREWNiHP3G+Kcg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=29931@debbugs.gnu.org \
--cc=alan@idiocy.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).