diff options
-rw-r--r-- | README | 22 |
1 files changed, 10 insertions, 12 deletions
@@ -78,10 +78,10 @@ recommend installing GNU libmicrohttpd (download from | |||
78 | http://www.gnu.org/software/libmicrohttpd/). Then you can start the | 78 | http://www.gnu.org/software/libmicrohttpd/). Then you can start the |
79 | actual GNUnet compilation and installation process with: | 79 | actual 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 | |||
94 | permissions and thus won't work. | 94 | permissions and thus won't work. |
95 | 95 | ||
96 | This will create the users and groups needed for running GNUnet | 96 | This will create the users and groups needed for running GNUnet |
97 | securely and then compile and install GNUnet to $GNUNET_PREFIX/bin/, | 97 | securely 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 |
99 | with the default configuration. It is strongly recommended that you | 99 | with the default configuration. It is strongly recommended that you |
100 | add a user "gnunet" to run "gnunet-arm". You can then still run the | 100 | add a user "gnunet" to run "gnunet-arm". You can then still run the |
101 | end-user applications as another user. | 101 | end-user applications as another user. |
@@ -128,7 +128,7 @@ those plugins, so you might need to do some additional manual work to | |||
128 | include those libraries in your binary package(s). Similarly, if you | 128 | include those libraries in your binary package(s). Similarly, if you |
129 | want to use the GNUnet naming system and did NOT run GNUnet's 'make | 129 | want to use the GNUnet naming system and did NOT run GNUnet's 'make |
130 | install' process with SUDO rights, the libraries will be installed to | 130 | install' 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/" |
132 | manually. | 132 | manually. |
133 | 133 | ||
134 | Finally, if you are compiling the code from subversion, you have to | 134 | Finally, 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 | ||
164 | GNUnet uses two types of configuration files, one that specifies the | 164 | GNUnet uses two types of configuration files, one that specifies the |
165 | system-wide defaults (typically located in | 165 | system-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 |
167 | default values with user-specific preferences. The user-specific | 167 | default values with user-specific preferences. The user-specific |
168 | configuration file should be located in "~/.config/gnunet.conf" or its | 168 | configuration file should be located in "~/.config/gnunet.conf" or its |
169 | location can be specified by giving the "-c" option to the respective | 169 | location 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 | |||
236 | report bugs can be found in the GNUnet FAQ on the webpage. Submit | 236 | report bugs can be found in the GNUnet FAQ on the webpage. Submit |
237 | patches via E-Mail to gnunet-developers@gnu.org. | 237 | patches via E-Mail to gnunet-developers@gnu.org. |
238 | 238 | ||
239 | In order to run the unit tests with "make check", you need to | 239 | In order to run the unit tests with by hand (instead of using |
240 | "make check"), you need to | ||
240 | set an environment variable ("GNUNET_PREFIX") to the directory | 241 | set an environment variable ("GNUNET_PREFIX") to the directory |
241 | where GNUnet is installed (usually, GNUnet will use OS specific | 242 | where GNUnet's libraries are installed. |
242 | tricks in order to try to figure out the PREFIX, but since the | 243 | Also, before running any testcases, you must |
243 | testcase binaries are not installed, that trick does not work | ||
244 | for them). Also, before running any testcases, you must | ||
245 | complete the installation first. Quick summary: | 244 | complete 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 | ||
253 | Some of the testcases require python >= 2.6 and pexpect to be | 251 | Some of the testcases require python >= 2.6 and pexpect to be |