From: Philipp Stephani <p.stephani2@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 28571@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#28571: 25.3; Compile error on macOS Sierra
Date: Sat, 30 Sep 2017 19:17:33 +0000 [thread overview]
Message-ID: <CAArVCkQ8p27te4hB-StUyounbt8yuwW=gjU5uCfOvjMmhy7gAg@mail.gmail.com> (raw)
In-Reply-To: <wl7ewnboxx.wl%mituharu@math.s.chiba-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> schrieb am Mo., 25. Sep.
2017 um 02:29 Uhr:
> >>>>> On Sun, 24 Sep 2017 07:49:55 +0000, Philipp Stephani <
> p.stephani2@gmail.com> said:
>
> >> I take it you upgraded Xcode the other day? (To version 9, I
> >> think?)
> >>
>
> > Yes, indeed.
>
> 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.
[-- Attachment #2: Type: text/html, Size: 1298 bytes --]
next prev parent reply other threads:[~2017-09-30 19:17 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 [this message]
2017-10-01 5:51 ` YAMAMOTO Mitsuharu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAArVCkQ8p27te4hB-StUyounbt8yuwW=gjU5uCfOvjMmhy7gAg@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=28571@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.