Compiling in MacOS X - Revision history

Nairnj: /* Convince Apple-Installed clang to Compile for OpenMP */

2026-03-28T23:35:15Z

Convince Apple-Installed clang to Compile for OpenMP

← Older revision		Revision as of 23:35, 28 March 2026
Line 136:		Line 136:
	\| align="center" \| 13.0 to 13.2.1 \|\| openmp-12.0.1-darwin20-Release.tar.gz		\| align="center" \| 13.0 to 13.2.1 \|\| openmp-12.0.1-darwin20-Release.tar.gz
	\|}		\|}
	If you have a newer version of XCode, you can check the [https://mac.r-project.org/openmp/ R project posting] for a new file name. If you have an older version of XCode, now is a good time to update your Mac.</li>		If you have a newer version of XCode, you can check the [https://mac.r-project.org/openmp/ R project posting] for a new file name or the newest one above may still work. If you have an older version of XCode, now is a good time to update your Mac.</li>
	<li>Once you have the file name, download it from <tt>r-project.org</tt> in the Terminal app using:		<li>Once you have the file name, download it from <tt>r-project.org</tt> in the Terminal app using:
	<pre>curl -O https://mac.r-project.org/openmp/openmp-15.0.7-darwin20-Release.tar.gz</pre>		<pre>curl -O https://mac.r-project.org/openmp/openmp-15.0.7-darwin20-Release.tar.gz</pre>

Nairnj: /* Convince Apple-Installed clang to Compile for OpenMP */

2026-03-28T23:27:35Z

Convince Apple-Installed clang to Compile for OpenMP

← Older revision		Revision as of 23:27, 28 March 2026
Line 122:		Line 122:
	! XCode Version !! File name to download		! XCode Version !! File name to download
	\|-		\|-
	\| align="center" \| 16.3+ \|\|		\| align="center" \| 16.3+ \|\| openmp-19.1.5-darwin20-Release.tar.gz
	\|-		\|-
	\| align="center" \| 16.0-16.2 \|\| openmp-17.0.6-darwin20-Release.tar.gz		\| align="center" \| 16.0-16.2 \|\| openmp-17.0.6-darwin20-Release.tar.gz

Nairnj: /* Convince Apple-Installed clang to Compile for OpenMP */

2026-03-28T23:26:52Z

Convince Apple-Installed clang to Compile for OpenMP

← Older revision		Revision as of 23:26, 28 March 2026
Line 121:		Line 121:
	\|-		\|-
	! XCode Version !! File name to download		! XCode Version !! File name to download
			\|-
			\| align="center" \| 16.3+ \|\|
	\|-		\|-
	\| align="center" \| 16.0-16.2 \|\| openmp-17.0.6-darwin20-Release.tar.gz		\| align="center" \| 16.0-16.2 \|\| openmp-17.0.6-darwin20-Release.tar.gz

Nairnj: /* Convince Apple-Installed clang to Compile for OpenMP */

2026-03-28T23:25:36Z

Convince Apple-Installed clang to Compile for OpenMP

← Older revision		Revision as of 23:25, 28 March 2026
Line 121:		Line 121:
	\|-		\|-
	! XCode Version !! File name to download		! XCode Version !! File name to download
			\|-
			\| align="center" \| 16.0-16.2 \|\| openmp-17.0.6-darwin20-Release.tar.gz
	\|-		\|-
	\| align="center" \| 15.0+ \|\| openmp-16.0.4-darwin20-Release.tar.gz		\| align="center" \| 15.x \|\| openmp-16.0.4-darwin20-Release.tar.gz
	\|-		\|-
	\| align="center" \| 14.3.x \|\| openmp-15.0.7-darwin20-Release.tar.gz		\| align="center" \| 14.3.x \|\| openmp-15.0.7-darwin20-Release.tar.gz

Nairnj: /* Possible Changes Needed After Updating MacOS or XCode */

2024-04-09T21:37:56Z

Possible Changes Needed After Updating MacOS or XCode

← Older revision		Revision as of 21:37, 9 April 2024
Line 226:		Line 226:
	# Reinstall command line tools in Terminal app by entering <tt>xcode-select --install</tt>		# Reinstall command line tools in Terminal app by entering <tt>xcode-select --install</tt>
	# Agree to XCode license in Terminal app using <tt>sudo xcodebuild -license</tt> (and provide your admin password).		# Agree to XCode license in Terminal app using <tt>sudo xcodebuild -license</tt> (and provide your admin password).
	# If you are using [[#Convince Apple-Installed clang to Compile for OpenMP\|Apple's compiler]] you may need to update the <tt>libomp.dylib</tt> library ~~that is not provided with Apple's command-line tools~~.		# If you are using [[#Convince Apple-Installed clang to Compile for OpenMP\|Apple's compiler]] you may need to update the <tt>libomp.dylib</tt> library for your new version of XCode.
	# If you are using MacPorts, you may need to uninstall it, install MacPorts for new MacOS, and then reinstall all previously installed ports. The process is explained in [https://trac.macports.org/wiki/Migration Migrating a MacPorts Installation]. Sometimes a "clean" install is best, especially after a major MacOS update. See [https://trac.macports.org/wiki/previous links] for details, but here is a brief outline of the process:		# If you are using MacPorts, you may need to uninstall it, install MacPorts for new MacOS, and then reinstall all previously installed ports. The process is explained in [https://trac.macports.org/wiki/Migration Migrating a MacPorts Installation]. Sometimes a "clean" install is best, especially after a major MacOS update. See [https://trac.macports.org/wiki/previous links] for details, but here is a brief outline of the process:
	## [https://guide.macports.org/chunked/installing.macports.uninstalling.html Uninstall all of MacPorts]		## [https://guide.macports.org/chunked/installing.macports.uninstalling.html Uninstall all of MacPorts]

Nairnj: /* Project Settings for clang-mp */

2024-04-09T21:36:46Z

Project Settings for clang-mp

← Older revision		Revision as of 21:36, 9 April 2024
Line 210:		Line 210:
	<li><b>Other C++ Flags</b>: add <tt>$(OTHER_CFLAGS)</tt> to have same flags used for C++ compile as well.</li>		<li><b>Other C++ Flags</b>: add <tt>$(OTHER_CFLAGS)</tt> to have same flags used for C++ compile as well.</li>
	<li><b>Header Search Paths</b>: add <tt>/opt/local/include/libomp</tt>		<li><b>Header Search Paths</b>: add <tt>/opt/local/include/libomp</tt>
	<li>Scroll to bottom of build settings to see the "User-Defined" settings. If <b>CC</b>, <b>CLANG_CXX_LIBRARY</b>, and <b>LDPLUSPLUS</b> are already there, make sure the <tt>clang-mp</tt> version numbers in <b>CC</b> and <b>LDPLUSPLUS</b> corresponds to one you have [[#~~Compiling for OpenMP~~\|installed]] or edit them to match your installed version. If any "User-Defined" settings are missible, add them with:		<li>Scroll to bottom of build settings to see the "User-Defined" settings. If <b>CC</b>, <b>CLANG_CXX_LIBRARY</b>, and <b>LDPLUSPLUS</b> are already there, make sure the <tt>clang-mp</tt> version numbers in <b>CC</b> and <b>LDPLUSPLUS</b> corresponds to one you have [[#Install clang-mp Compiler\|installed]] or edit them to match your installed version. If any "User-Defined" settings are missible, add them with:
	<ol>		<ol>
	<li>Use menu command Editor→Add Build Setting→Add User-Defined Setting and add setting for <b>CC</b> with value <b>/opt/local/bin/clang-mp-11</b> (using clang version number you installed).</li>		<li>Use menu command Editor→Add Build Setting→Add User-Defined Setting and add setting for <b>CC</b> with value <b>/opt/local/bin/clang-mp-11</b> (using clang version number you installed).</li>

Nairnj: /* Project Setting for Apple's Compiler */

2024-04-09T21:34:58Z

Project Setting for Apple's Compiler

← Older revision		Revision as of 21:34, 9 April 2024
Line 194:		Line 194:
	<li><b>Runpath Search Paths</b>: remove <tt>/opt/local/libexec/llvm-17/lib</tt> (or with other clang version number) if it is there.</li>		<li><b>Runpath Search Paths</b>: remove <tt>/opt/local/libexec/llvm-17/lib</tt> (or with other clang version number) if it is there.</li>
	<li><b>Header Search Paths</b>: remove <tt>/opt/local/include/libomp</tt> if it is there</li>		<li><b>Header Search Paths</b>: remove <tt>/opt/local/include/libomp</tt> if it is there</li>
	<li><b>Other C Flags</b>: add <tt>-Xclang -fopenmp</tt> (replacing <tt>-fopenmp</tt> if there).</li>		<li><b>Other C Flags</b>: add <tt>-Xclang -fopenmp</tt> together as a single flag (replacing <tt>-fopenmp</tt> if there).</li>
	<li><b>Other C++ Flags</b>: add <tt>$(OTHER_CFLAGS)</tt> to have same flags used for C++ compile as well.</li>		<li><b>Other C++ Flags</b>: add <tt>$(OTHER_CFLAGS)</tt> to have same flags used for C++ compile as well.</li>
	<li>Scroll to bottom of build settings to see the "User-Defined" settings. If <b>CC</b>, <b>CLANG_CXX_LIBRARY</b>, and <b>LDPLUSPLUS</b> are there, delete them be selecting and using the delete key.</li>		<li>Scroll to bottom of build settings to see the "User-Defined" settings. If <b>CC</b>, <b>CLANG_CXX_LIBRARY</b>, and <b>LDPLUSPLUS</b> are there, delete them be selecting and using the delete key.</li>

Nairnj: /* Install clang-mp Compiler */

2024-04-09T21:32:49Z

Install clang-mp Compiler

← Older revision		Revision as of 21:32, 9 April 2024
Line 175:		Line 175:
	# Although these versions get installed, you may need to verify the [[#Project Settings for clang-mp\|XCode project settings]] match both your installed version of <tt>clang-mp</tt> and your choice to use a separate compiler. A new issue occurs in MacOS Sonoma, but that is corrected with a new [[#Project Settings for clang-mp\|runpath project setting]]. Future MacOS's might cause more problems and some might be fixable with new project settings.		# Although these versions get installed, you may need to verify the [[#Project Settings for clang-mp\|XCode project settings]] match both your installed version of <tt>clang-mp</tt> and your choice to use a separate compiler. A new issue occurs in MacOS Sonoma, but that is corrected with a new [[#Project Settings for clang-mp\|runpath project setting]]. Future MacOS's might cause more problems and some might be fixable with new project settings.

	You can install multiple versions of <tt>clang-mp</tt>, which can be useful if working with multiple checkouts of this project. More likely, you ~~will~~ only need ~~only~~ one version. If you settle on one version, you can remove older ones with		You can install multiple versions of <tt>clang-mp</tt>, which can be useful if working with multiple checkouts of this project. More likely, you only need one version. If you settle on one version, you can remove older ones with

	sudo port uninstall --follow-dependents clang-xx		sudo port uninstall --follow-dependents clang-xx

Nairnj: /* Install clang-mp Compiler */

2024-04-09T21:32:17Z

Install clang-mp Compiler

← Older revision		Revision as of 21:32, 9 April 2024
Line 173:		Line 173:
	# A MacPorts <tt>install</tt> command in MacOS Sonoma reports that <tt>clang-mp</tt> versions 11, 12, and 13 are "known to fail." It appears these version can still be installed, but the <tt>sudo port install</tt> may not finish. If it exits without a binary, repeat the <tt>install</tt> command until it (hopefully) finishes. Each repeat picks up where it left off. If it hangs up while installing, force exit with Control-C and repeat again. If it eventually finishes, the install seems to work. I needed three repeats for one successful install of <tt>clang-mp-11</tt>.		# A MacPorts <tt>install</tt> command in MacOS Sonoma reports that <tt>clang-mp</tt> versions 11, 12, and 13 are "known to fail." It appears these version can still be installed, but the <tt>sudo port install</tt> may not finish. If it exits without a binary, repeat the <tt>install</tt> command until it (hopefully) finishes. Each repeat picks up where it left off. If it hangs up while installing, force exit with Control-C and repeat again. If it eventually finishes, the install seems to work. I needed three repeats for one successful install of <tt>clang-mp-11</tt>.
	# Installing <tt>clang-mp</tt> versions 14 or newer in MacOS Sonoma does not say "known to fail", but the first <tt>install</tt> command may exit with an unexpected "permission denied" error. Repeating the <tt>install</tt> command then picks up where it left off and finishes the install.		# Installing <tt>clang-mp</tt> versions 14 or newer in MacOS Sonoma does not say "known to fail", but the first <tt>install</tt> command may exit with an unexpected "permission denied" error. Repeating the <tt>install</tt> command then picks up where it left off and finishes the install.
	# Although these versions get installed, you may need to verify the [[#Project Settings for clang-mp\|XCode project settings]] match both ~~you~~ installed version of <tt>clang-mp</tt> and ~~you~~ choice to use a separate ~~compile~~. A new issue occurs in MacOS Sonoma, but that is corrected with a new [[#Project Settings for clang-mp\|runpath project ~~settings~~]]. Future MacOS's might cause more problems and some might be fixable with new project settings.		# Although these versions get installed, you may need to verify the [[#Project Settings for clang-mp\|XCode project settings]] match both your installed version of <tt>clang-mp</tt> and your choice to use a separate compiler. A new issue occurs in MacOS Sonoma, but that is corrected with a new [[#Project Settings for clang-mp\|runpath project setting]]. Future MacOS's might cause more problems and some might be fixable with new project settings.

	You can install multiple versions of <tt>clang-mp</tt>, which can be useful if working with multiple checkouts of this project. More likely, you will only need only one version. If you settle on one version, you can remove older ones with		You can install multiple versions of <tt>clang-mp</tt>, which can be useful if working with multiple checkouts of this project. More likely, you will only need only one version. If you settle on one version, you can remove older ones with

Nairnj: /* Install clang-mp Compiler */

2024-04-09T21:30:22Z

Install clang-mp Compiler

← Older revision		Revision as of 21:30, 9 April 2024
Line 172:		Line 172:

	# A MacPorts <tt>install</tt> command in MacOS Sonoma reports that <tt>clang-mp</tt> versions 11, 12, and 13 are "known to fail." It appears these version can still be installed, but the <tt>sudo port install</tt> may not finish. If it exits without a binary, repeat the <tt>install</tt> command until it (hopefully) finishes. Each repeat picks up where it left off. If it hangs up while installing, force exit with Control-C and repeat again. If it eventually finishes, the install seems to work. I needed three repeats for one successful install of <tt>clang-mp-11</tt>.		# A MacPorts <tt>install</tt> command in MacOS Sonoma reports that <tt>clang-mp</tt> versions 11, 12, and 13 are "known to fail." It appears these version can still be installed, but the <tt>sudo port install</tt> may not finish. If it exits without a binary, repeat the <tt>install</tt> command until it (hopefully) finishes. Each repeat picks up where it left off. If it hangs up while installing, force exit with Control-C and repeat again. If it eventually finishes, the install seems to work. I needed three repeats for one successful install of <tt>clang-mp-11</tt>.
	# Installing <tt>clang-mp</tt> versions 14 or newer in MacOS Sonoma does not say "known to fail", but the first <tt>install</tt> command may exit with an unexpected "permission denied" error. Repeating the <tt>install</tt> command then picks up where it left off and finishes the install. Although these versions get installed, ~~a new issue appears when compiling~~ the ~~code. See~~ [[#~~XCode Build~~ Settings\|XCode project settings]] ~~for details on changing the XCode project file to switch to new versions~~ of <tt>clang-mp</tt>.		# Installing <tt>clang-mp</tt> versions 14 or newer in MacOS Sonoma does not say "known to fail", but the first <tt>install</tt> command may exit with an unexpected "permission denied" error. Repeating the <tt>install</tt> command then picks up where it left off and finishes the install.
	~~# The~~ [[#~~XCode Build~~ Settings\|~~XCode~~ project settings]] might ~~need to change to match [[#Compiling for OpenMP\|your compiler]] or to fix other issues caused by MacOS "upgrades~~."		# Although these versions get installed, you may need to verify the [[#Project Settings for clang-mp\|XCode project settings]] match both you installed version of <tt>clang-mp</tt> and you choice to use a separate compile. A new issue occurs in MacOS Sonoma, but that is corrected with a new [[#Project Settings for clang-mp\|runpath project settings]]. Future MacOS's might cause more problems and some might be fixable with new project settings.

	You can install multiple versions of <tt>clang-mp</tt>, which can be useful if working with multiple checkouts of this project. More likely, you will only need only one version. If you settle on one version, you can remove older ones with		You can install multiple versions of <tt>clang-mp</tt>, which can be useful if working with multiple checkouts of this project. More likely, you will only need only one version. If you settle on one version, you can remove older ones with