From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 28571@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#28571: 25.3; Compile error on macOS Sierra
Date: Sun, 01 Oct 2017 14:51:30 +0900 [thread overview]
Message-ID: <wlpoa7xvod.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <CAArVCkQ8p27te4hB-StUyounbt8yuwW=gjU5uCfOvjMmhy7gAg@mail.gmail.com>
>>>>> On Sat, 30 Sep 2017 19:17:33 +0000, Philipp Stephani <p.stephani2@gmail.com> said:
>> Probably You need to execute "$ xcode-select --install" to install
>> Command Line Tools for Xcode. You can actually go without it by
>> tweaking some environment variables and/or compiler arguments, but
>> I wouldn't recommend that unless you have a shortage of disk space
>> and you really understand what you are doing.
>>
>>
> OK, the warning is indeed gone after that, thanks. Should we put
> something in configure.ac that checks for this? It's a bit subtle
> because compilation almost completely works without it.
Installation of the Command Line Tools is not a strict requirement.
For example, the Nix package manager does not require Xcode but use
its own SDK, IIUC. On the other hand, MacPorts and Homebrew
explicitly require users to install the Command Line Tools:
https://www.macports.org/install.php
https://docs.brew.sh/Installation.html
I guess nowadays most users use some package manager. If they are
following its installation instructions correctly, they are in a
correct configuration. Otherwise, they will face another problem
sooner or later anyway.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2017-10-01 5:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 19:08 bug#28571: 25.3; Compile error on macOS Sierra Philipp
2017-09-23 19:31 ` Alan Third
2017-09-24 7:49 ` Philipp Stephani
2017-09-24 11:06 ` Alan Third
2017-09-24 11:23 ` Philipp Stephani
2017-09-24 12:09 ` Alan Third
2017-09-28 18:07 ` Alan Third
2017-09-29 7:23 ` Eli Zaretskii
2017-09-25 0:29 ` YAMAMOTO Mitsuharu
2017-09-30 19:17 ` Philipp Stephani
2017-10-01 5:51 ` YAMAMOTO Mitsuharu [this message]
2017-09-28 20:58 ` mituharu
2017-09-28 21:39 ` Alan Third
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=wlpoa7xvod.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=28571@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=p.stephani2@gmail.com \
/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).