From ddd0baca07e1e64bf08b5fd3e93c819d2c1906ec Mon Sep 17 00:00:00 2001 From: brson Date: Thu, 13 Sep 2012 21:29:06 -0700 Subject: [PATCH] Don't even mention --enable-debug --- Note-getting-started-developing-Rust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Note-getting-started-developing-Rust.md b/Note-getting-started-developing-Rust.md index 757e74c..09a5fc6 100644 --- a/Note-getting-started-developing-Rust.md +++ b/Note-getting-started-developing-Rust.md @@ -68,7 +68,7 @@ This will build and test the compiler, standard libraries, and supporting tools. *Note:* You can use `make -j8` (if you have an 8-core machine) to speed up the build (at least the LLVM part and the tests). On Linux or OS X, if you have Valgrind installed, the tests will run slowly because they are running under Valgrind. If you define `CFG_DISABLE_VALGRIND=1` in your build environment or run configure with the `--disable-valgrind` flag, you can see the tests running at full speed. -If you are going to be hacking on the Rust compiler itself then it is recommended that you configure with `--disable-optimize`, since this will greatly speed up your compilation. If you use `--enable-debug`, expect some test failures in class-related tests ([bug #2194](https://github.com/mozilla/rust/issues/2194)). +If you are going to be hacking on the Rust compiler itself then it is recommended that you configure with `--disable-optimize`, since this will greatly reduce up your compilation time. ## Packages