aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2015-01-09 07:23:18 +0000
committerChristian Grothoff <christian@grothoff.org>2015-01-09 07:23:18 +0000
commitb191726bb6653b5fd08305b87951b7d3c8cdf0fb (patch)
treee9e842118ff7e128b2e1cfdbcaaf35ea5694ecdb /README
parent7ac778d075ddde3743f426a5fd8d2e06e1a12796 (diff)
downloadgnunet-b191726bb6653b5fd08305b87951b7d3c8cdf0fb.tar.gz
gnunet-b191726bb6653b5fd08305b87951b7d3c8cdf0fb.zip
-update docu to reflect current use of GNUNET_PREFIX
Diffstat (limited to 'README')
-rw-r--r--README22
1 files changed, 10 insertions, 12 deletions
diff --git a/README b/README
index 1700c4f8e..98d77b907 100644
--- a/README
+++ b/README
@@ -78,10 +78,10 @@ recommend installing GNU libmicrohttpd (download from
78http://www.gnu.org/software/libmicrohttpd/). Then you can start the 78http://www.gnu.org/software/libmicrohttpd/). Then you can start the
79actual GNUnet compilation and installation process with: 79actual GNUnet compilation and installation process with:
80 80
81$ export GNUNET_PREFIX=/usr/local # or other directory of your choice 81$ export GNUNET_PREFIX=/usr/local/lib # or other directory of your choice
82# addgroup gnunetdns 82# addgroup gnunetdns
83# adduser gnunet gnunet 83# adduser gnunet gnunet
84# ./configure --prefix=$GNUNET_PREFIX --with-extractor=$LE_PREFIX 84# ./configure --prefix=$GNUNET_PREFIX/.. --with-extractor=$LE_PREFIX
85$ make 85$ make
86# make install 86# make install
87# sudo -u gnunet gnunet-arm -s 87# sudo -u gnunet gnunet-arm -s
@@ -94,8 +94,8 @@ may not be installed in the perfect place or with the right
94permissions and thus won't work. 94permissions and thus won't work.
95 95
96This will create the users and groups needed for running GNUnet 96This will create the users and groups needed for running GNUnet
97securely and then compile and install GNUnet to $GNUNET_PREFIX/bin/, 97securely and then compile and install GNUnet to $GNUNET_PREFIX/../bin/,
98$GNUNET_PREFIX/lib/ and $GNUNET_PREFIX/share/ and start the system 98$GNUNET_PREFIX/ and $GNUNET_PREFIX/../share/ and start the system
99with the default configuration. It is strongly recommended that you 99with the default configuration. It is strongly recommended that you
100add a user "gnunet" to run "gnunet-arm". You can then still run the 100add a user "gnunet" to run "gnunet-arm". You can then still run the
101end-user applications as another user. 101end-user applications as another user.
@@ -128,7 +128,7 @@ those plugins, so you might need to do some additional manual work to
128include those libraries in your binary package(s). Similarly, if you 128include those libraries in your binary package(s). Similarly, if you
129want to use the GNUnet naming system and did NOT run GNUnet's 'make 129want to use the GNUnet naming system and did NOT run GNUnet's 'make
130install' process with SUDO rights, the libraries will be installed to 130install' process with SUDO rights, the libraries will be installed to
131"$GNUNET_PREFIX/lib" and you will have to move them to "/lib/" 131"$GNUNET_PREFIX" and you will have to move them to "/lib/"
132manually. 132manually.
133 133
134Finally, if you are compiling the code from subversion, you have to 134Finally, if you are compiling the code from subversion, you have to
@@ -163,7 +163,7 @@ about the GNU build process read the INSTALL file.
163 163
164GNUnet uses two types of configuration files, one that specifies the 164GNUnet uses two types of configuration files, one that specifies the
165system-wide defaults (typically located in 165system-wide defaults (typically located in
166$GNUNET_PREFIX/share/gnunet/config.d/) and a second one that overrides 166$GNUNET_PREFIX/../share/gnunet/config.d/) and a second one that overrides
167default values with user-specific preferences. The user-specific 167default values with user-specific preferences. The user-specific
168configuration file should be located in "~/.config/gnunet.conf" or its 168configuration file should be located in "~/.config/gnunet.conf" or its
169location can be specified by giving the "-c" option to the respective 169location can be specified by giving the "-c" option to the respective
@@ -236,18 +236,16 @@ and include the output with your bug reports. More about how to
236report bugs can be found in the GNUnet FAQ on the webpage. Submit 236report bugs can be found in the GNUnet FAQ on the webpage. Submit
237patches via E-Mail to gnunet-developers@gnu.org. 237patches via E-Mail to gnunet-developers@gnu.org.
238 238
239In order to run the unit tests with "make check", you need to 239In order to run the unit tests with by hand (instead of using
240"make check"), you need to
240set an environment variable ("GNUNET_PREFIX") to the directory 241set an environment variable ("GNUNET_PREFIX") to the directory
241where GNUnet is installed (usually, GNUnet will use OS specific 242where GNUnet's libraries are installed.
242tricks in order to try to figure out the PREFIX, but since the 243Also, before running any testcases, you must
243testcase binaries are not installed, that trick does not work
244for them). Also, before running any testcases, you must
245complete the installation first. Quick summary: 244complete the installation first. Quick summary:
246 245
247$ ./configure --prefix=$SOMEWHERE 246$ ./configure --prefix=$SOMEWHERE
248$ make 247$ make
249$ make install 248$ make install
250$ export GNUNET_PREFIX=$SOMEWHERE
251$ make check 249$ make check
252 250
253Some of the testcases require python >= 2.6 and pexpect to be 251Some of the testcases require python >= 2.6 and pexpect to be