renamed S2EPREFIX to S2E_PREFIX, inline with build-scripts

S2E · Jul 26, 2018 · 64dd17b · 64dd17b
1 parent 9513300
commit 64dd17b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/BuildingS2E.rst b/src/BuildingS2E.rst
@@ -150,7 +150,7 @@ The S2E Makefile can be run as follows:
     # Go make some coffee, this will take some time (approx. 60 mins on a 4-core machine)
 
 By default, the ``make`` command compiles and installs S2E in release mode to ``$S2EDIR/build/opt``. To change this
-location, set the ``S2EPREFIX`` environment variable when running ``make``.
+location, set the ``S2E_PREFIX`` environment variable when running ``make``.
 
 To compile S2E in Debug mode, use ``make install-debug``.
 

diff --git a/src/Tutorials/BasicLinuxSymbex/s2e.so.rst b/src/Tutorials/BasicLinuxSymbex/s2e.so.rst
@@ -15,7 +15,7 @@ Obtaining and compiling ``s2e.so``
 
 The ``s2e.so`` library can be found in the ``guest`` folder of the S2E distribution and is built during the standard
 S2E build process. It can also be built by running ``make guest-tools-install``. This will create ``guest-tools32`` and
-``guest-tools64`` in ``$S2EDIR/build-s2e/$S2EPREFIX/bin`` (remember that by default ``$S2EPREFIX`` is equal to
+``guest-tools64`` in ``$S2EDIR/build-s2e/$S2E_PREFIX/bin`` (remember that by default ``$S2E_PREFIX`` is equal to
 ``opt``). Copy the directory matching your guest's architecture into the guest virtual machine.
 
 Configuring S2E for use with ``s2e.so``