FATE_SAMPLES is now used directly by the Makefiles, which induces the test
system to try to run a test the the value of the environment variable as name.
Renaming the environment variable to FATE_SAMPLES_DIR avoids this problem.
---
 configure     |    4 ++--
 doc/fate.texi |    4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/configure b/configure
index fcba059..4176899 100755
--- a/configure
+++ b/configure
@@ -259,7 +259,7 @@ Developer options (useful when working on Libav itself):
   --disable-optimizations  disable compiler optimizations
   --enable-extra-warnings  enable more compiler warnings
   --samples=PATH           location of test samples for FATE, if not set use
-                           \$FATE_SAMPLES at make invocation time.
+                           \$FATE_SAMPLES_DIR at make invocation time.
   --enable-xmm-clobber-test check XMM registers for clobbering (Win64-only;
                            should be used only for debugging purposes)
 
@@ -3377,7 +3377,7 @@ SLIB_INSTALL_NAME=${SLIB_INSTALL_NAME}
 SLIB_INSTALL_LINKS=${SLIB_INSTALL_LINKS}
 SLIB_INSTALL_EXTRA_LIB=${SLIB_INSTALL_EXTRA_LIB}
 SLIB_INSTALL_EXTRA_SHLIB=${SLIB_INSTALL_EXTRA_SHLIB}
-SAMPLES:=${samples:-\$(FATE_SAMPLES)}
+SAMPLES:=${samples:-\$(FATE_SAMPLES_DIR)}
 EOF
 
 get_version(){
diff --git a/doc/fate.texi b/doc/fate.texi
index 5489d95..5a8cbc7 100644
--- a/doc/fate.texi
+++ b/doc/fate.texi
@@ -26,8 +26,8 @@ that is provided separately from the actual source 
distribution.
 
 To inform the build system about the testsuite location, pass
 @option{--samples=<path to the samples>} to @command{configure} or set the
-@var{SAMPLES} Make variable or the @var{FATE_SAMPLES} environment variable
-to a suitable value.
+@var{SAMPLES} Make variable or the @var{FATE_SAMPLES_DIR} environment
+variable to a suitable value.
 
 The dataset is available through @command{rsync}, is possible to fetch
 the current sample using the straight rsync command or through a specific
-- 
1.7.1

_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to