singa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wan...@apache.org
Subject [10/13] incubator-singa git commit: SINGA-72 Minor updates to be consisten with documentation
Date Sun, 27 Sep 2015 14:34:33 GMT
SINGA-72 Minor updates to be consisten with documentation

Comment the installation instructions for protocol buffer python libs.

Update readme file to install all dependent libs into PREFIX.


Project: http://git-wip-us.apache.org/repos/asf/incubator-singa/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-singa/commit/88e2ba32
Tree: http://git-wip-us.apache.org/repos/asf/incubator-singa/tree/88e2ba32
Diff: http://git-wip-us.apache.org/repos/asf/incubator-singa/diff/88e2ba32

Branch: refs/heads/master
Commit: 88e2ba32734ebae5551234bc63e613da48f83c67
Parents: 321ef96
Author: Wei Wang <wangwei@comp.nus.edu.sg>
Authored: Sun Sep 27 10:47:01 2015 +0800
Committer: Wei Wang <wangwei@comp.nus.edu.sg>
Committed: Sun Sep 27 10:47:01 2015 +0800

----------------------------------------------------------------------
 README.md             | 43 ++++++++++++++++++++++++++++++++++---------
 thirdparty/install.sh | 16 ++++++++--------
 2 files changed, 42 insertions(+), 17 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-singa/blob/88e2ba32/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index bf7874a..5e20ded 100644
--- a/README.md
+++ b/README.md
@@ -25,11 +25,17 @@ You can install all dependencies into $PREFIX folder by
 
     ./thirdparty/install.sh all $PREFIX
 
+You can also install these libraries one by one. The usage is listed by
+
+    ./thidparty/install.sh
+
 If $PREFIX is not a system path (e.g., /usr/local/), you have to export some
 environment variables,
 
     export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH
-    export CPLUS_INCLUDE_PATH=$PREFIX/include
+    export CPLUS_INCLUDE_PATH=$PREFIX/include:$CPLUS_INCLUDE_PATH
+    export LIBRARY_PATH=$PREFIX/lib:$LIBRARY_PATH
+    export PATH=$PREFIX/bin:$PATH
 
 ##Documentation
 
@@ -81,15 +87,15 @@ For additional information, see the LICENSE and NOTICE files.
 ## FAQ
 
 * Q1:I get error `./configure --> cannot find blas_segmm() function` even I
-run `install.sh OpenBLAS`.
+have installed OpenBLAS.
 
-  A1: `OpenBLAS` library is installed in `/opt` folder by default or
+  A1: `OpenBLAS` library is installed in `/opt` folder by default or $PREFIX or
   other folders if you use `sudo apt-get install`.
-  You need to include the OpenBLAS library folder in the LDFLAGS, e.g.,
+  You need to export the OpenBLAS library folder, e.g.,
 
-      $ export LDFLAGS=-L/opt/OpenBLAS
-
-  Alternatively, you can include the path in LIBRARY_PATH.
+      $ export LIBRARY_PATH=$PREFIX/lib:$LIBRARY_PATH
+      # or
+      $ export LIBRARY_PATH=/opt/OpenBLAS/lib:$LIBRARY_PATH
 
 
 * Q2: I get error `cblas.h no such file or directory exists`.
@@ -98,6 +104,8 @@ run `install.sh OpenBLAS`.
   e.g.,
 
       $ export CPLUS_INCLUDE_PATH=/opt/OpenBLAS/include:$CPLUS_INCLUDE_PATH
+      # or
+      $ export CPLUS_INCLUDE_PATH=$PREFIX/include:$CPLUS_INCLUDE_PATH
       # reconfigure and make SINGA
       $ ./configure
       $ make
@@ -158,10 +166,27 @@ google.protobuf.internal when I try to import .py files.
 
   or install it using
 
-	  $ sudo apt-get install openblas
+	    $ sudo apt-get install openblas
 
   or
 
-	  $ sudo yum install openblas-devel
+	    $ sudo yum install openblas-devel
 
   It is worth noting that you need root access to run the last two commands.
+
+* Q9: When I build protocol buffer, it reports that GLIBC++_3.4.20 not found in /usr/lib64/libstdc++.so.6.
+
+  A9: This means the linker found libstdc++.so.6 but that library
+  belongs to an older version of GCC than was used to compile and link the
+  program. The program depends on code defined in
+  the newer libstdc++ that belongs to the newer version of GCC, so the linker
+  must be told how to find the newer libstdc++ shared library.
+  The simplest way to fix this is to find the correct libstdc++ and export it to
+  LD_LIBRARY_PATH. For example, if GLIBC++_3.4.20 is listed in the output of the
+  following command,
+
+      $ strings /usr/local/lib64/libstdc++.so.6|grep GLIBC++
+
+  then you just set your environment variable as
+
+      $ export LD_LIBRARY_PATH=/usr/local/lib64:$LD_LIBRARY_PATH

http://git-wip-us.apache.org/repos/asf/incubator-singa/blob/88e2ba32/thirdparty/install.sh
----------------------------------------------------------------------
diff --git a/thirdparty/install.sh b/thirdparty/install.sh
index 86211d6..9e7b73f 100755
--- a/thirdparty/install.sh
+++ b/thirdparty/install.sh
@@ -258,19 +258,19 @@ function install_protobuf()
 			echo "install protobuf in $1";
 			./configure --prefix=$1;
 			make && make install;
-			cd python;
-			python setup.py build;
-			python setup.py install --prefix=$1;
-			cd ..;
+			#cd python;
+			#python setup.py build;
+			#python setup.py install --prefix=$1;
+			#cd ..;
 		elif [ $# == 0 ]
 		then
 			echo "install protobuf in default path";
 			./configure;
 			make && sudo make install;
-			cd python;
-			python setup.py build;
-			sudo python setup.py install;
-			cd ..;
+			#cd python;
+			#python setup.py build;
+			#sudo python setup.py install;
+			#cd ..;
 		else
 			echo "wrong commands";
 	fi


Mime
View raw message