[libav-commits] faq: Solutions for common problems with sample paths when running FATE.

Diego Biurrun git at libav.org
Sat Jan 7 20:54:10 CET 2012


Module: libav
Branch: master
Commit: 8b1a26864c875c956bf16c4869eaa8b6c80cd9ff

Author:    Diego Biurrun <diego at biurrun.de>
Committer: Diego Biurrun <diego at biurrun.de>
Date:      Fri Dec 30 23:14:14 2011 +0100

faq: Solutions for common problems with sample paths when running FATE.

---

 doc/faq.texi |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/doc/faq.texi b/doc/faq.texi
index 8044200..7c5373c 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -359,4 +359,16 @@ to use them you have to append -D__STDC_CONSTANT_MACROS to your CXXFLAGS
 You have to implement a URLProtocol, see @file{libavformat/file.c} in
 Libav and @file{libmpdemux/demux_lavf.c} in MPlayer sources.
 
+ at section Why is @code{make fate} not running all tests?
+
+Make sure you have the fate-suite samples and the @code{SAMPLES} Make variable
+or @code{FATE_SAMPLES} environment variable or the @code{--samples}
+ at command{configure} option is set to the right path.
+
+ at section Why is @code{make fate} not finding the samples?
+
+Do you happen to have a @code{~} character in the samples path to indicate a
+home directory? The value is used in ways where the shell cannot expand it,
+causing FATE to not find files. Just replace @code{~} by the full path.
+
 @bye



More information about the libav-commits mailing list