(e.g. Intel Linux icc compiler) write temporary files to the current
directory. These compilers do support -c and -o simultaneously but
wrongly fail the test due to the failure to create temporary
files. It is incorrect to penalize compilers which write temporary
files to the current directory so the 'chmod -w .' is therefore
removed.
+2004-01-22 Jeff Squyres <jsquyres@lam-mpi.org>
+
+ * m4/libtool.m4 (AC_LIBTOOL_PROG_CC_C_O): Some compilers
+ (e.g. Intel Linux icc compiler) write temporary files to the current
+ directory. These compilers do support -c and -o simultaneously but
+ wrongly fail the test due to the failure to create temporary
+ files. It is incorrect to penalize compilers which write temporary
+ files to the current directory so the 'chmod -w .' is therefore
+ removed.
+
2004-01-22 Gary V. Vaughan <gary@gnu.org>
* m4/libtool.m4 (LT_AC_PROG_EGREP): Wrapper for AC_PROG_GREP.
mkdir out
printf "$lt_simple_compile_test_code" > conftest.$ac_ext
- # According to Tom Tromey, Ian Lance Taylor reported there are C compilers
- # that will create temporary files in the current directory regardless of
- # the output directory. Thus, making CWD read-only will cause this test
- # to fail, enabling locking or at least warning the user not to do parallel
- # builds.
- chmod -w .
-
lt_compiler_flag="-o out/conftest2.$ac_objext"
# Insert the option either (1) after the last *FLAGS variable, or
# (2) before a word containing "conftest.", or (3) at the end.