[MacPorts] UsingTheRightCompiler modified

[MacPorts]

Page "UsingTheRightCompiler" was changed by cal at macports.org
Diff URL: <https://trac.macports.org/wiki/UsingTheRightCompiler?action=diff&version=19>
Revision 19
Comment: remove references to gcc_select, which is no longer the way to change the default compiler
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: UsingTheRightCompiler
=========================================================================
--- UsingTheRightCompiler (version: 18)
+++ UsingTheRightCompiler (version: 19)
@@ -16,7 +16,7 @@
 
 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,
 or on Tiger to downgrade to gcc 3.3 to compile old software that is not compatible with gcc 4.
@@ -27,11 +27,11 @@
 The problem is further complicated by the various gcc ports which can be installed using MacPorts,
 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.
 To remove this testing burden from maintainers,
@@ -40,7 +40,7 @@
 and does not use the unpredictable "`gcc`".
 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.
 
 In fact there are more variables than just CC:
-------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 .