aboutsummaryrefslogtreecommitdiffstats
path: root/xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf
diff options
context:
space:
mode:
authorLukas Larsson <[email protected]>2012-08-24 12:02:58 +0200
committerLukas Larsson <[email protected]>2012-08-24 12:02:58 +0200
commit0342137176c653c51cc3a78781888cfca8568650 (patch)
treeb3f2b462589a7d574a80e4557a8a05a222184a3e /xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf
parentdd12380a68f4692c1aba2e972b84de89f3df46df (diff)
parent85283dc19ceea2905ff39aa0615d1a99d7aea16c (diff)
downloadotp-0342137176c653c51cc3a78781888cfca8568650.tar.gz
otp-0342137176c653c51cc3a78781888cfca8568650.tar.bz2
otp-0342137176c653c51cc3a78781888cfca8568650.zip
Merge branch 'msp/double_middle_endian/OTP-10209' into maint
* msp/double_middle_endian/OTP-10209: Configure now assumed normal doubles Revise the autoconf tests for double middle endianness. Add test for floating-point output to float_SUITE. Unbreak floating point on middle-endian machines.
Diffstat (limited to 'xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf')
-rw-r--r--xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf9
1 files changed, 9 insertions, 0 deletions
diff --git a/xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf b/xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf
index be22d498d6..e86043f5c8 100644
--- a/xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf
+++ b/xcomp/erl-xcomp-avr32-atmel-linux-gnu.conf
@@ -190,6 +190,15 @@ erl_xcomp_sysroot="$ATMEL_SYSROOT_AVR32"
# value is used, `configure' will try to figure this out automatically.
#erl_xcomp_bigendian=
+# * `erl_xcomp_double_middle_endian` - `yes|no`. No default. If `yes`, the
+# target system must have doubles in "middle-endian" format. If
+# `no`, it has "regular" endianness. This can often be automatically
+# detected, but not always. If not automatically detected,
+# `configure` will fail unless this variable is set. Since no
+# default value is used, `configure` will try to figure this out
+# automatically.
+#erl_xcomp_double_middle_endian
+
# * `erl_xcomp_clock_gettime_cpu_time' - `yes|no'. Defaults to `no'. If `yes',
# the target system must have a working `clock_gettime()' implementation
# that can be used for retrieving process CPU time.