2008-03-21 Eric Blake <ebb9@byu.net>
+ Document more uses of $cross_compiling.
+ * doc/autoconf.texi (Runtime): Document that a temporary override
+ is permissible.
+ * THANKS: Update.
+ Reported by Ineiev, example by Ralf Wildenhues.
+
Don't swallow $1 in textual local variables.
* lib/m4sugar/m4sugar.m4 (m4_combine): Don't use overquoting and
expansion of text arguments, as that swallows $1.
Ian Macdonald iamacdo@telkomsa.net
Ian Redfern Ian.Redfern@logicacmg.com
Ilya Zakharevich ilya@Math.Berkeley.EDU
+Ineiev ineiev@yahoo.co.uk
Iohannes m zmoelnig zmoelnig@iem.at
J C Fitzgerald v7022@wave.co.nz
Jaap Haitsma jaap@haitsma.org
@samp{yes}, and then use an alternate method to get the results instead
of calling the macros.
+It is also permissible to temporarily assign to @code{cross_compiling}
+in order to force tests to behave as though they are in a
+cross-compilation environment, particularly since this provides a way to
+test your @var{action-if-cross-compiling} even when you are not using a
+cross-compiler.
+
+@example
+# We temporarily set cross-compile mode to force AC_COMPUTE_INT
+# to use the slow link-only method
+save_cross_compiling=$cross_compiling
+cross_compiling=yes
+AC_COMPUTE_INT([@dots{}])
+cross_compiling=$save_cross_compiling
+@end example
+
A C or C++ runtime test should be portable.
@xref{Portable C and C++}.