* 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.
This commit is contained in:
Jeff Squyres 2004-01-22 19:01:19 +00:00 committed by Bob Friesenhahn
parent a9d07029d6
commit 0085cef913
2 changed files with 10 additions and 7 deletions

View File

@ -1,3 +1,13 @@
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.

7
m4/libtool.m4 vendored
View File

@ -1311,13 +1311,6 @@ AC_CACHE_CHECK([if $compiler supports -c -o file.$ac_objext],
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.