From e6a44d41b92bd6d8db005edfcf5cd75d3e22b3a5 Mon Sep 17 00:00:00 2001
From: diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>
Date: Mon, 30 Oct 2006 21:28:44 +0000
Subject: [PATCH] Explain the risks of forcing options with --enable-* in a way
 that is hopefully less conducive to misunderstandings.

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@20541 b3059339-0415-0410-9bf9-f77b7e298cf2
---
 configure | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/configure b/configure
index b68b026d72..3b593f4ef1 100755
--- a/configure
+++ b/configure
@@ -8469,11 +8469,17 @@ fi
 
 
 cat <<EOF
+Check $TMPLOG if you wonder why an autodetection failed (make sure
+development headers/packages are installed).
 
-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).
+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.