docs: Minor fix in install guide (INSTALLING.md)
Makefile: lzma is required while building

The following error was produced when -llzma is not specified:

$ make check
cc -O2 -fPIC -Wimplicit -I../include -c ../test/test_extension/test.c -o ../test/test_extension/test.o -g
cc -shared ../test/test_extension/test.o -o ../test/test_extension/test.so -g
pyston: Compiling runtime/inline/link_forcer.o.bc
pyston: Compiling ../tools/publicize.o
pyston: Linking ../tools/publicize
elfxx.c:193: error: undefined reference to 'lzma_stream_footer_decode'
elfxx.c:200: error: undefined reference to 'lzma_index_buffer_decode'
elfxx.c:204: error: undefined reference to 'lzma_index_size'
elfxx.c:209: error: undefined reference to 'lzma_index_end'
elfxx.c:206: error: undefined reference to 'lzma_index_uncompressed_size'
elfxx.c:209: error: undefined reference to 'lzma_index_end'
elfxx.c:277: error: undefined reference to 'lzma_stream_buffer_decode'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [../tools/publicize] Error 1
tests: adjust time_test to fix test failure on some distributions

Result of "import time; print time" can be various from different
distributions, for example:

$ python -c "import time; print time"
<module 'time' from '/usr/lib64/python2.7/lib-dynload/timemodule.so'>

which is diff from the result of "<module 'time' (built-in)>".

So test with result of "print type(time)" instead, which should be
more robust.
Makefile: include gtest headers with '-isystem'

gtest does not compile successfully with "-Wundef", so the following
error will be produced while running unittests:

$ make run_gc_unittests

<snip>
 /path-to-deps/gtest-1.7.0/include/gtest/internal/gtest-port.h:288:6: error: 'GTEST_OS_WINDOWS' is not defined,
       evaluates to 0 [-Werror,-Wundef]
 #if !GTEST_OS_WINDOWS
     ^
 /path-to-deps/gtest-1.7.0/include/gtest/internal/gtest-port.h:299:5: error: 'GTEST_OS_LINUX_ANDROID' is not defined,
       evaluates to 0 [-Werror,-Wundef]
 #if GTEST_OS_LINUX_ANDROID
     ^
<snip>

The workaround for this issue is using '-isystem'.