This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[patch] 6.1: Use AC_C_LONG_DOUBLE for autoconf 2.5x
- From: "Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>
- To: Daniel Jacobowitz <drow at false dot org>,gdb-patches at sources dot redhat dot com
- Date: Wed, 19 May 2004 16:10:31 +0200 (CEST)
- Subject: [patch] 6.1: Use AC_C_LONG_DOUBLE for autoconf 2.5x
- Organization: Technical University of Gdansk
Hello,
As of autoconf 2.5x AC_C_LONG_DOUBLE works correctly for a
cross-compilation. Hence a private replacement is no longer needed once
gdb/ is converted. Here's a patch.
2004-05-19 Maciej W. Rozycki <macro@ds2.pg.gda.pl>
* configure.in: Use AC_C_LONG_DOUBLE instead of a private
replacement.
* configure: Regenerate.
Maciej
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
gdb-5.2-long-double.patch
diff -up --recursive --new-file gdb-5.2.macro/gdb/configure.in gdb-5.2/gdb/configure.in
--- gdb-5.2.macro/gdb/configure.in 2002-03-28 04:28:00.000000000 +0000
+++ gdb-5.2/gdb/configure.in 2002-05-15 20:13:49.000000000 +0000
@@ -459,18 +459,9 @@ if test $gdb_cv_printf_has_long_long = y
fi
AC_MSG_RESULT($gdb_cv_printf_has_long_long)
-dnl See if compiler supports "long double" type. Can't use AC_C_LONG_DOUBLE
-dnl because autoconf complains about cross-compilation issues. However, this
-dnl code uses the same variables as the macro for compatibility.
-
-AC_MSG_CHECKING(for long double support in compiler)
-AC_CACHE_VAL(ac_cv_c_long_double,
-[AC_TRY_COMPILE(, [long double foo;],
-ac_cv_c_long_double=yes, ac_cv_c_long_double=no)])
-AC_MSG_RESULT($ac_cv_c_long_double)
-if test $ac_cv_c_long_double = yes; then
- AC_DEFINE(HAVE_LONG_DOUBLE)
-fi
+dnl See if compiler supports "long double" type.
+
+AC_C_LONG_DOUBLE
dnl See if the compiler and runtime support printing long doubles