Commit 6a6d049c authored by Kevin Modzelewski's avatar Kevin Modzelewski

Remove pyston_gcc from `make check`

I don't think we regularly run make check anymore, and it's a pain
to make sure the user has an up-to-date gcc (would need to come up
with a good set of instructions for anyone on 12.04).  So just remove
it from make check for now.
parent b8cd6e68
......@@ -17,7 +17,9 @@ USE_DISTCC := 0
ENABLE_VALGRIND := 0
GDB := gdb
GCC_DIR := $(DEPS_DIR)/gcc-4.8.2-install
# If you followed the old install instructions:
# GCC_DIR := $(DEPS_DIR)/gcc-4.8.2-install
GCC_DIR := /usr
GTEST_DIR := $(DEPS_DIR)/gtest-1.7.0
USE_DEBUG_LIBUNWIND := 0
......@@ -544,11 +546,6 @@ check:
$(MAKE) run_unittests ARGS=
@# Building in gcc mode is helpful to find various compiler-specific warnings.
@# We've also discovered UB in our code from running in gcc mode, so try running it as well.
$(MAKE) pyston_gcc
$(PYTHON) $(TOOLS_DIR)/tester.py -R pyston_gcc -j$(TEST_THREADS) -k -a=-S $(TESTS_DIR) $(ARGS)
$(MAKE) pyston_release
@# It can be useful to test release mode, since it actually exposes different functionality
@# since we can make different decisions about which internal functions to inline or not.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment