Fix erroneous USE_LONG_DOUBLE in configure.com.

Once upon a time there was a "use64bit" option [1] that only later
became separated into use64bitint, uselongdouble, and use64bitall,
but we didn't properly separate out everything.  So if you chose
64-bit integers but not long doubles, you would get the macro
USE_LONG_DOUBLE defined but without other supporting defines and
with incompatible branches followed in various parts of the #ifdef
jungle.  So separate them out.  Thanks to Thomas Pfau for trying
what's apparently a rare configuration.

[1] See fafa4fee6354847ae7fda.

diff --git a/configure.com b/configure.com
index 941b6caddfc5e0944f3bdc337a79f7295e719876..42b8733ae6949176bcf164330c6df2eaefe5449f 100644 (file)
--- a/configure.com
+++ b/configure.com
@@ -6914,6 +6914,9 @@ $ IF d_alwdeftype THEN WC "#define ALWAYS_DEFTYPES"
 $ IF use64bitint .OR. use64bitint .EQS. "define"
 $ THEN
 $   WC "#define USE_64_BIT_INT"
+$ ENDIF
+$ IF uselongdouble .OR. uselongdouble .EQS. "define"
+$ THEN
 $   WC "#define USE_LONG_DOUBLE"
 $ ENDIF
 $ IF use64bitall .OR. use64bitall .EQS. "define" THEN -