valitydev/riak_test
14
0
Fork 0
mirror of https://github.com/valitydev/riak_test.git synced 2024-11-06 16:45:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove HiPE flag of kerl configure instructions

Browse Source 
We disabled HiPE on all builders from 1.2 going forward.
This change is a minor nitpick to make sure dev setups
are as close to possible to what we deliver.
This commit is contained in:
Jared Morrow 2012-09-10 11:53:11 -06:00
parent 2c42591521
commit 4816b0c672
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -2,7 +2,7 @@
## Bootstraping Your Test Environment ## Bootstraping Your Test Environment
Welcome to the exciting world of riak_test. Running tests against a development version of Riak is just one of the things that you can do with riak_test. You can also test things involving upgrading from previous versions of Riak. Together, we'll get your test environment up and running. Scripts to help in this process are located in the `bin` directory of this project. Welcome to the exciting world of riak_test. Running tests against a development version of Riak is just one of the things that you can do with riak_test. You can also test things involving upgrading from previous versions of Riak. Together, we'll get your test environment up and running. Scripts to help in this process are located in the `bin` directory of this project.
### rtdev-build-releases.sh ### rtdev-build-releases.sh
The first one that we want to look at is `rtdev-build-releases.sh`. If left unchanged, this script is going to do the following: The first one that we want to look at is `rtdev-build-releases.sh`. If left unchanged, this script is going to do the following:
@ -20,7 +20,7 @@ R14B04=${R14B04:-$HOME/erlang-R14B04}
**Kerlveat**: If you want kerl to build erlangs with serious 64-bit macintosh action, you'll need a `~/.kerlrc` file that looks like this: **Kerlveat**: If you want kerl to build erlangs with serious 64-bit macintosh action, you'll need a `~/.kerlrc` file that looks like this:
``` ```
KERL_CONFIGURE_OPTIONS="--enable-hipe --enable-smp-support --enable-threads --enable-kernel-poll --enable-darwin-64bit" KERL_CONFIGURE_OPTIONS="--enable-smp-support --enable-threads --enable-kernel-poll --enable-darwin-64bit"
``` ```
The script will check that all these paths exist. If even one of them is missing, it will prompt you to install kerl, even if you already have kerl. If you say no, the script quits. If you say yes, or all of your erlang paths check out, then go get a cup of coffee, you'll be building for a little while. The script will check that all these paths exist. If even one of them is missing, it will prompt you to install kerl, even if you already have kerl. If you say no, the script quits. If you say yes, or all of your erlang paths check out, then go get a cup of coffee, you'll be building for a little while.
@ -55,4 +55,3 @@ Now that you've got your releases all ready and gitified, you'll need to tell ri
Run a test! `./riak_test rtdev_mixed verify_build_cluster` Run a test! `./riak_test rtdev_mixed verify_build_cluster`
Did that work? Great, try something harder: `./riak_test rtdev_mixed upgrade` Did that work? Great, try something harder: `./riak_test rtdev_mixed upgrade`