drop coi and scif from native builds, and document it

doc/doxygen/chapters/18mic_scc_support.doxy

@@ -23,6 +23,14 @@ for the host and for the mic, one can use <c>--with-host-param=--with-fxt</c>
 for instance to specify the <c>--with-fxt</c> option for the host only, or
 <c>--with-mic-param=--with-fxt</c> for the mic only.
 
+One can also run StarPU just natively on the Xeon Phi, i.e. it will only run
+directly on the Phi without any exchange with the host CPU. The binaries in
+<c>build_mic</c> can be run that way.
+
+In case you have troubles with the coi or scif libraries (the Intel paths are
+really not standard, it seems...), you can still make a build in native mode
+only, by using <c>mic-configure --enable-native-mic</c>
+
 \section PortingApplicationsToMICSCC Porting Applications To MIC Xeon Phi / SCC
 
 The simplest way to port an application to MIC Xeon Phi or SCC is to set the field

mic-configure

@@ -84,12 +84,17 @@ do
 	    export CXXLD="icc -mmic"
 	fi
 
-	params="--enable-mic --with-coi-dir=$coi_dir --with-scif-dir=$scif_dir --prefix=$prefix/$arch"
+	params="--prefix=$prefix/$arch"
+
+	if [ "$native_mic" -eq "0" ]
+	then
+	    params="$params --enable-mic --with-coi-dir=$coi_dir --with-scif-dir=$scif_dir"
+	fi
 
 	if test x$arch = xmic ; then
 	    if [ "$native_mic" -eq "1" ]
 	    then
-		params="$params --disable-build-doc --with-coi-lib-dir=$coi_dir/device-linux-release/lib --with-scif-lib-dir=$scif_dir/device-linux-release/lib --host=$mic_host --enable-maxcpus=250"
+		params="$params --disable-build-doc --host=$mic_host --enable-maxcpus=250"
 	    else
 		params="$params --disable-build-doc --with-coi-lib-dir=$coi_dir/device-linux-release/lib --with-scif-lib-dir=$scif_dir/device-linux-release/lib --host=$mic_host"
 	    fi