(Compilation Functions): Add xref to Problems with Macros.

diff --git a/lispref/compile.texi b/lispref/compile.texi
index 001466d500d1de9edccb96b5ba90313294dcb630..b854fc86edfa81e4a630ae4347c64fe7fad1d8f5 100644 (file)
--- a/lispref/compile.texi
+++ b/lispref/compile.texi
@@ -110,7 +110,9 @@ program that suggest a problem but are not necessarily erroneous.
   Be careful when writing macro calls in files that you may someday
 byte-compile.  Macro calls are expanded when they are compiled, so the
 macros must already be defined for proper compilation.  For more
-details, see @ref{Compiling Macros}.
+details, see @ref{Compiling Macros}.  If a program does not work the
+same way when compiled as it does when interpreted, erroneous macro
+definitions are one likely cause (@pxref{Problems with Macros}).
 
   Normally, compiling a file does not evaluate the file's contents or
 load the file.  But it does execute any @code{require} calls at top