[MacPorts] UsingTheRightCompiler modified

[MacPorts]

Page "UsingTheRightCompiler" was changed by larryv at macports.org
Diff URL: <https://trac.macports.org/wiki/UsingTheRightCompiler?action=diff&version=18>
Revision 18
Comment: add title
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: UsingTheRightCompiler
=========================================================================
--- UsingTheRightCompiler (version: 17)
+++ UsingTheRightCompiler (version: 18)
@@ -1,4 +1,6 @@
-= Introduction = #introduction
+= Using the Right Compiler =
+
+== Introduction == #introduction
 
 Much of the software in MacPorts is built using a C or C++ compiler,
 and the various versions of Xcode for OS X come with different compiler suites and versions.
@@ -10,7 +12,7 @@
 The Xcode 4.6 release notes state that it is the last version of Xcode that will include llvm-gcc-4.2, which will leave only clang.
 
 
-= The problem with the default compiler = #default-compiler
+== The problem with the default compiler == #default-compiler
 
 The default version of gcc can be run simply as "`gcc`".
 There's also "`cc`" which points to the default compiler (which might not necessarily be gcc).
@@ -49,7 +51,7 @@
 ${configure.cc}, ${configure.cxx} and ${configure.cpp}.
 
 
-= Selecting a different compiler = #configure-compiler
+== Selecting a different compiler == #configure-compiler
 
 For most ports,
 the default compiler chosen by MacPorts is the one that should be used,
@@ -103,7 +105,7 @@
 additional environment variables FC, F77 and F90 are set to the path of the Fortran compiler.
 These variables are not set for the other compilers because they do not include a Fortran compiler.
 
-= Ports with nonstandard or nonexistent configure scripts = #nonstandard-ports
+== Ports with nonstandard or nonexistent configure scripts == #nonstandard-ports
 
 Setting the CC, CXX and CPP environment variables at configure time
 is all that most software needs in order to use the compiler we want.
@@ -124,7 +126,7 @@
 Such patches should usually be sent upstream for inclusion in the next version of the software.
 
 
-= How to test = #testing
+== How to test == #testing
 
 Unless you look closely at the build output in debug mode,
 it can be hard to know whether a port is using ${configure.cc} as it should.
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/UsingTheRightCompiler>
MacPorts <http://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'UsingTheRightCompiler' page.
If it was not you, please report to .