Differences

This shows you the differences between two versions of the page.

--- en:release:2.86_release_notes [2017/02/24 05:03] – [Enabling user comments] anupama
+++ en:release:2.86_release_notes [2017/09/27 05:27] – [Source Components and Source Distributions] anupama
@@ Line 107: / Line 107: @@
 ./makegli.sh
 ./makejar.sh
-</code> \\ **Note** that some Linux machines don't need gnome-lib at all, in which case, the first compilation step above would just be ''./makegs2.sh''. To tell whether your Linux machine needs gnome-lib, try compiling it without it first. If compilation fails during wvware, then you need gnome-lib. The Mac Mountain Lion and Leopard machines we tested it on required gnome-lib.
+</code>
+**Note** that some Linux and Mac machines may require to you to ''export CFLAGS="-fPIC $CFLAGS"'' before running the ''./makegs2.sh script''. If compilation fails when the ''CFLAGS'' has not been set to include ''-fPIC'', then try
+<pre>export CFLAGS="-fPIC $CFLAGS"
+make distclean
+makegs2.sh</pre>
+**Note** also that some Linux machines don't need gnome-lib at all, in which case, the first compilation step above would just be ''./makegs2.sh''. To tell whether your Linux machine needs gnome-lib, try compiling it without it first. If compilation fails during wvware, then you need gnome-lib. The Mac Mountain Lion and Leopard machines we tested it on required gnome-lib.
 </TAB>
 <!-----Source comp Win----->
@@ Line 506: / Line 512: @@
 These instructions are more Greenstone 2.86-specific than the [[http://wiki.greenstone.org/wiki/index.php/Remote_Greenstone|general instructions]] for setting up Greenstone 2 as a remote server.
-The following are steps to follow if you're on **Windows**. On **Linux**, you can skip steps 1 and 2, otherwise things are similar. For instance, you'll want to launch *.bash or *.sh script equivalents to the batch files listed. Also, you'll want to use forward slashes (/) instead of the Windows' backward slash (\) when specifying file paths.
+The following are steps to follow if you're on **Windows**. On **Unix based systems**, you can skip steps 1 and 2, otherwise things are similar. For instance, on Unix systems, you'll want to launch *.bash or *.sh script equivalents to the batch files listed. Also, you'll want to use forward slashes (/) instead of the Windows' backward slash (\) when specifying file paths.