changeset 20525:d598cd751a00

Explain the risks of forcing options with --enable-* in a way that is hopefully less conducive to misunderstandings.
author diego
date Mon, 30 Oct 2006 21:28:44 +0000
parents 655565aafbe4
children d61a365dbe87
files configure
diffstat 1 files changed, 11 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/configure	Mon Oct 30 21:25:02 2006 +0000
+++ b/configure	Mon Oct 30 21:28:44 2006 +0000
@@ -8469,11 +8469,17 @@
 
 
 cat <<EOF
-
-Check $TMPLOG if you wonder why an autodetection failed (check whether
-the development headers/packages are installed).
-Do not report compilation errors if you used any of the --enable-* options
-(except --enable-gui and maybe --enable-debug).
+Check $TMPLOG if you wonder why an autodetection failed (make sure
+development headers/packages are installed).
+
+NOTE: The --enable-* parameters unconditionally force options on, completely
+skipping autodetection. This behavior is unlike what you may be used to from
+autoconf-based configure scripts that can decide to override you. This greater
+level of control comes at a price. You may have to provide the correct compiler
+and linker flags yourself.
+If you used one of these options (except --enable-gui and similar ones that
+turn on internal features) and experience a compilation or linking failure,
+make sure you have passed the necessary compiler/linker flags to configure.
 
 If you suspect a bug, please read DOCS/HTML/$_doc_lang/bugreports.html.