From: yanke131415@gmail.com
To: git@vger.kernel.org
Cc: out0fmemory <jiu4majia2@163.com>
Subject: [PATCH] INSTALL: add macOS gettext and sdk header explanation to INSTALL
Date: Wed, 14 Nov 2018 18:38:30 +0800 [thread overview]
Message-ID: <20181114103830.20434-1-yanke131415@gmail.com> (raw)
From: out0fmemory <jiu4majia2@163.com>
---
INSTALL | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/INSTALL b/INSTALL
index c39006e8e7..b7bfb53c12 100644
--- a/INSTALL
+++ b/INSTALL
@@ -165,6 +165,9 @@ Issues of note:
use English. Under autoconf the configure script will do this
automatically if it can't find libintl on the system.
+ In macOS, can install and link gettext with brew as "brew install gettext"
+ and "brew link --force gettext", the link operation is necessary.
+
- Python version 2.4 or later (but not 3.x, which is not
supported by Perforce) is needed to use the git-p4 interface
to Perforce.
@@ -178,6 +181,10 @@ Issues of note:
will include them. Note that config.mak is not distributed;
the name is reserved for local settings.
+ - In macOs 10.14, the Command Line Tool not contains the headers as before, so it
+ need install Command Line Tool 10.14 and install the headers which command
+ "sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target".
+
- To build and install documentation suite, you need to have
the asciidoc/xmlto toolchain. Because not many people are
inclined to install the tools, the default build target
--
2.19.1.1052.gd166e6afe5
next reply other threads:[~2018-11-14 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 10:38 yanke131415 [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-15 1:32 [PATCH] INSTALL: add macOS gettext and sdk header explanation to INSTALL yanke131415
2018-11-15 3:05 ` Jonathan Nieder
2018-11-15 10:42 ` yan ke
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=20181114103830.20434-1-yanke131415@gmail.com \
--to=yanke131415@gmail.com \
--cc=git@vger.kernel.org \
--cc=jiu4majia2@163.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox