No commit message

compilation.markdown

@@ -55,11 +55,21 @@ Building fat extensions:
 ```
 This will compile both 32- and 64-bit versions of the extensions on non-OS-X systems. On non-OS-X systems the building of native messaging (Chrome) extension will be avoided. On OS X all the generated binaries will be fat (containing 32- and 64-bit versions). (Useful when creating a distributable package. We use Debian 7 to build Linux packages.)
 
+If you have several C compiler versions on your system and if you want to compile the extension using a different compiler version (e.g. gcc-4.4) than the default one then use these commands:
+
+``` shell
+# Libtool crashes when OBJC not specified.
+./configure CC=gcc-4.4 OBJC=gcc-4.4 --enable-static-linking --with-force-abi=fat
+make CC=gcc-4.4 OBJC=gcc-4.4
+```
+
+### Targeting Windows
+
 Cross compiling using MinGW32:
 ``` shell
 ./scripts/build_with_mingw32.sh
 ```
-This will prepare and generate a 32-bit package for Windows. Currently we use `i586-mingw32msvc`. Other versions of MinGW fail to build the binary cores.
+This will prepare and generate a 32-bit package for Windows. Currently we use `i586-mingw32msvc`.
 
 Creating Chrome package:
 ``` shell
@@ -69,20 +79,6 @@ make
 ```
 You need to have the package keys needed to signing the extension located in the parrent directory where the validator source tree is located.
 
-### Specifying Compiler Version
-
-If you have several C compiler versions on your system and if you want to compile the extension using a different compiler version (e.g. gcc-4.4) than the default one then use these commands:
-
-``` shell
-# Force 32-bit extension
-./configure CC=gcc-4.4 OBJC=gcc-4.4 --enable-static-linking --with-force-abi=x86
-make CC=gcc-4.4 OBJC=gcc-4.4
-
-# Force 64-bit extension
-./configure CC=gcc-4.4 OBJC=gcc-4.4 --enable-static-linking --with-force-abi=x86_64
-make CC=gcc-4.4 OBJC=gcc-4.4
-```
-
 **Building extensions for Safari is currently not supported.**
 
 **Building of NPAPI based extensions is currently not supported.**