[MacPorts] FAQ modified

[MacPorts]

Changed page "FAQ" by jmr at macports.org from 202.7.166.167*
Page URL: <http://trac.macports.org/wiki/FAQ>
Diff URL: <http://trac.macports.org/wiki/FAQ?action=diff&version=81>
Revision 81
Comment: improve port build failure suggestions

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 80)
+++ FAQ (version: 81)
@@ -4,9 +4,9 @@
 
 == General Questions ==
 
-=== A port fails to build === #buildfails
-
-Before filing a bug in the issue tracker, please make sure you have the latest version of MacPorts and of the ports tree by running
+=== A port fails to build. What should I do? === #buildfails
+
+Before filing a ticket in the issue tracker, please make sure you have the latest version of MacPorts and of the ports tree by running
 
 {{{
 sudo port selfupdate
@@ -20,7 +20,9 @@
 
 Also, make sure you have the latest version of Xcode. Old versions of Xcode are known to make certain ports fail.
 
-=== I get the error "C compiler cannot create executables" when I try to install a port === #missingxcode
+If this does not help, check ProblemHotlist (and SnowLeopardProblems if you are on Mac OS X 10.6) and see if your issue is mentioned. If not, [search:] for an existing ticket. If there does not appear to be one, you can then [http://guide.macports.org/#project.tickets create a new ticket].
+
+=== I get the error "C compiler cannot create executables" when I try to install a port. Why? === #missingxcode
 
 You need to install [http://www.macports.org/install.php#requirements Xcode].
 Ensure you include both X11SDK and Unix Development.

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on FAQ. If it was not you, please
report to .