Changes between Version 1 and Version 2 of UsingTheRightCompiler

Timestamp:

Jun 4, 2009, 5:50:18 AM (15 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

add section on detecting ports that aren't using ${configure.cc} et al

UsingTheRightCompiler

@@ -107 +107 @@
 possibly in combination with setting ${build.env} as above.
 Such patches should usually be sent upstream for inclusion in the next version of the software.
+
+
+= 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.
+Here is one strategy that can be used:
+
+ 1. Create a directory /opt/local/bin/no_default_gcc
+ 2. Create a script in that directory called "`cc`" that always prints an error message
+ 3. Create symlinks "`c++`", "`cpp`", "`g++`", and "`gcc`", all pointing to the "`cc`" script
+ 4. Edit the value of "binpath" in /opt/local/etc/macports/macports.conf so that it begins with "/opt/local/bin/no_default_gcc:"
+
+Now anytime a port tries to use one of these unversioned programs, the compile will stop with an error.
+
+Steps 1 through 3 can be done
+by checking out [browser:users/ryandesign/no_default_gcc this directory]
+from the MacPorts Subversion repository:
+
+{{{
+svn checkout \
+http://svn.macosforge.org/repository/macports/users/ryandesign/no_default_gcc \
+/opt/local/bin/no_default_gcc
+}}}
+
+If you encounter a port which triggers this error
+but you don't want to fix it immediately,
+you can bypass it by editing macports.conf
+and removing "/opt/local/bin/no_default_gcc:" from the "binpath" again.