[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Caching the result of `-c -o'
From: |
Alexandre Oliva |
Subject: |
Caching the result of `-c -o' |
Date: |
11 Mar 2001 01:06:30 -0300 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) |
Here are patches that arrange for the result of the `-c -o' test to be
cached. The first one is for mainline, the second is for MLB. Ok to
install?
Index: ChangeLog
from Alexandre Oliva <address@hidden>
* libtool.m4 (lt_cv_compiler_c_o): Cache it.
(lt_cv_compiler_o_lo): Likewise.
Index: libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/libtool.m4,v
retrieving revision 1.149
diff -u -p -r1.149 libtool.m4
--- libtool.m4 2001/03/09 04:25:30 1.149
+++ libtool.m4 2001/03/11 02:59:49
@@ -1006,6 +1006,7 @@ can_build_shared="$lt_cv_prog_cc_can_bui
##
# Check to see if options -o and -c are simultaneously supported by compiler
AC_MSG_CHECKING([if $compiler supports -c -o file.$ac_objext])
+AC_CACHE_VAL([lt_cv_compiler_c_o], [
$rm -r conftest 2>/dev/null
mkdir conftest
cd conftest
@@ -1024,16 +1025,15 @@ if { (eval echo configure:__oline__: \"$
# The compiler can only warn and ignore the option if not recognized
# So say no if there are warnings
if test -s out/conftest.err; then
- compiler_c_o=no
+ lt_cv_compiler_c_o=no
else
- compiler_c_o=yes
+ lt_cv_compiler_c_o=yes
fi
else
# Append any errors to the config.log.
cat out/conftest.err 1>&AC_FD_CC
- compiler_c_o=no
+ lt_cv_compiler_c_o=no
fi
-AC_MSG_RESULT([$compiler_c_o])
CFLAGS="$save_CFLAGS"
chmod u+w .
$rm conftest* out/*
@@ -1041,24 +1041,30 @@ rmdir out
cd ..
rmdir conftest
$rm -r conftest 2>/dev/null
+])
+compiler_c_o=$lt_cv_compiler_c_o
+AC_MSG_RESULT([$compiler_c_o])
if test x"$compiler_c_o" = x"yes"; then
# Check to see if we can write to a .lo
AC_MSG_CHECKING([if $compiler supports -c -o file.lo])
- compiler_o_lo=no
+ AC_CACHE_VAL([lt_cv_compiler_o_lo], [
+ lt_cv_compiler_o_lo=no
save_CFLAGS="$CFLAGS"
CFLAGS="$CFLAGS -c -o conftest.lo"
AC_TRY_COMPILE([], [int some_variable = 0;], [dnl
# The compiler can only warn and ignore the option if not recognized
# So say no if there are warnings
if test -s conftest.err; then
- compiler_o_lo=no
+ lt_cv_compiler_o_lo=no
else
- compiler_o_lo=yes
+ lt_cv_compiler_o_lo=yes
fi
])
- AC_MSG_RESULT([$compiler_c_o])
CFLAGS="$save_CFLAGS"
+ ])
+ compiler_o_lo=$lt_cv_compiler_o_lo
+ AC_MSG_RESULT([$compiler_c_lo])
else
compiler_o_lo=no
fi
Index: ChangeLog
from Alexandre Oliva <address@hidden>
* ltconfig.in (lt_cv_compiler_c_o): Cache it.
* ltcf-gcj.sh (lt_cv_compiler_c_o): Set it.
Index: ltconfig.in
===================================================================
RCS file: /cvsroot/libtool/libtool/Attic/ltconfig.in,v
retrieving revision 1.246.2.50
diff -u -p -r1.246.2.50 ltconfig.in
--- ltconfig.in 2001/03/09 04:36:30 1.246.2.50
+++ ltconfig.in 2001/03/11 01:54:07
@@ -809,45 +809,48 @@ fi
# Check to see if options -o and -c are simultaneously supported by compiler
echo $ac_n "checking if $compiler supports -c -o file.$objext... $ac_c" 1>&6
-$rm -r conftest 2>/dev/null
-mkdir conftest
-cd conftest
-$rm conftest*
-echo $lt_simple_compile_test_code > conftest.$ac_ext
-mkdir out
-# 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 .
-save_CFLAGS="$CFLAGS"
-CFLAGS="$CFLAGS -o out/conftest2.$objext"
-echo "$progname:@LINENO@: checking if $compiler supports -c -o file.$objext"
>&5
-if { (eval echo $progname:@LINENO@: \"$ac_compile\") 1>&5; (eval $ac_compile)
2>out/conftest.err; } && test -s out/conftest2.$objext; then
-
- # The compiler can only warn and ignore the option if not recognized
- # So say no if there are warnings
- if test -s out/conftest.err; then
- echo "$ac_t"no 1>&6
- compiler_c_o=no
- else
- echo "$ac_t"yes 1>&6
- compiler_c_o=yes
- fi
+if test "${lt_cv_compiler_c_o+set}" = set; then
+ echo $ac_n "(cached) $ac_c" 1>&6
else
- # Append any errors to the config.log.
- cat out/conftest.err 1>&5
- compiler_c_o=no
- echo "$ac_t"no 1>&6
+ $rm -r conftest 2>/dev/null
+ mkdir conftest
+ cd conftest
+ $rm conftest*
+ echo $lt_simple_compile_test_code > conftest.$ac_ext
+ mkdir out
+ # 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 .
+ save_CFLAGS="$CFLAGS"
+ CFLAGS="$CFLAGS -o out/conftest2.$objext"
+ echo "$progname:@LINENO@: checking if $compiler supports -c -o file.$objext"
>&5
+ if { (eval echo $progname:@LINENO@: \"$ac_compile\") 1>&5; (eval
$ac_compile) 2>out/conftest.err; } && test -s out/conftest2.$objext; then
+
+ # The compiler can only warn and ignore the option if not recognized
+ # So say no if there are warnings
+ if test -s out/conftest.err; then
+ lt_cv_compiler_c_o=no
+ else
+ lt_cv_compiler_c_o=yes
+ fi
+ else
+ # Append any errors to the config.log.
+ cat out/conftest.err 1>&5
+ lt_cv_compiler_c_o=no
+ fi
+ CFLAGS="$save_CFLAGS"
+ chmod u+w .
+ $rm conftest* out/*
+ rmdir out
+ cd ..
+ rmdir conftest
+ $rm -r conftest 2>/dev/null
fi
-CFLAGS="$save_CFLAGS"
-chmod u+w .
-$rm conftest* out/*
-rmdir out
-cd ..
-rmdir conftest
-$rm -r conftest 2>/dev/null
+compiler_c_o=$lt_cv_compiler_c_o
+echo "${ac_t}$compiler_c_o" 1>&6
# Check to see if we can do hard links to lock some files if needed
hard_links="nottested"
Index: ltcf-gcj.sh
===================================================================
RCS file: /cvsroot/libtool/libtool/Attic/ltcf-gcj.sh,v
retrieving revision 1.1.2.15
diff -u -p -r1.1.2.15 ltcf-gcj.sh
--- ltcf-gcj.sh 2001/03/07 01:51:20 1.1.2.15
+++ ltcf-gcj.sh 2001/03/11 01:54:08
@@ -627,3 +627,6 @@ fi
# GCJ did not exist at the time GCC didn't implicitly link libc in.
need_lc=no
+
+# All existing releases of GCJ support `-c -o'.
+lt_cv_compiler_c_o=yes
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer address@hidden, redhat.com}
CS PhD student at IC-Unicamp address@hidden, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
- Caching the result of `-c -o',
Alexandre Oliva <=