Changes between Version 18 and Version 19 of UsingTheRightCompiler

Timestamp:

Apr 7, 2013, 5:38:46 PM (11 years ago)

Author:

neverpanic (Clemens Lang)

Comment:

remove references to gcc_select, which is no longer the way to change the default compiler

UsingTheRightCompiler

@@ -17 +17 @@
 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).
-The default gcc can be changed using the "`gcc_select`" command.
+The default gcc can be changed using the "`port select`" mechanism.
 Some users may have used this command to change their default gcc,
 for example on Leopard to test new functionality in gcc 4.2,
@@ -28 +28 @@
 which have different capabilities than the Apple versions of gcc.
 For example, only the Apple versions can create universal binaries in a single step.
-The gcc_select port can be used to make any of them the default compiler.
+The port select mechanism can be used to make any of them the default compiler.
 So we cannot rely on "`gcc`" being any particular version of gcc with any particular capabilities,
 and "`cc`" varies by Xcode version as well.
 
-Most port authors will not have used "`gcc_select`"
+Most port authors will not have used "`port select --set gcc $value`"
 and will therefore have the usual default version of gcc on their machine,
 and will not have tested to see what happens if a different gcc is selected.
@@ -41 +41 @@
 It does this by specifying the desired compiler's complete path in the CC environment variable
 during the port's configure phase.
-For example, on OS X 10.4 and 10.5, CC is set to the value "`/usr/bin/gcc-4.0`"
+For example, on OS X 10.8, CC is set to the value "`/usr/bin/clang`"
 so that there is no ambiguity.