From 7c469133a0692a20ea4db3f91a9a12b2a1a448be Mon Sep 17 00:00:00 2001 From: "Schanzenbach, Martin" Date: Mon, 4 Feb 2019 11:45:17 +0100 Subject: update macos instructions --- doc/system_specific/FROM_SOURCE | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) (limited to 'doc/system_specific') diff --git a/doc/system_specific/FROM_SOURCE b/doc/system_specific/FROM_SOURCE index 074b6a91e..72660798d 100644 --- a/doc/system_specific/FROM_SOURCE +++ b/doc/system_specific/FROM_SOURCE @@ -866,13 +866,13 @@ This means that you have to make sure the proper tools are used in the build pro For example, after installing texinfo you need to make sure the new texinfo is actually used: @example -# echo 'export PATH="/usr/local/opt/texinfo/bin:$PATH"' >> ~/.bash_profile +$ echo 'export PATH="/usr/local/opt/texinfo/bin:$PATH"' >> ~/.bash_profile @end example Note: brew tells you the appropriate command when executing @example -# brew info texinfo +$ brew info texinfo @end example This may also be necessary for the gettext package. @@ -881,9 +881,21 @@ Before you start compiling, you need to make sure gcc is used and not the clang On my system, gcc was actually ``gcc-7'' and gcc pointed to the clang compiler. @example -# export CC=gcc-7 +$ export CC=gcc-7 @end example +You might see configure failing telling you that it ``cannot run C compiled programs.''. +In this case, you might need to open/run Xcode once and you will be prompted to +install additonal packages. +Then, you might have to manually install the command line tools from here https://developer.apple.com/download/more/ (you need an Apple ID for this). +Install those and execute + +@example +$open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg +@end example + +Then, configure will pass again. + After this the standard compile instructions apply. @c @node Build instructions for OpenBSD 6.2 -- cgit v1.2.3