---
doc/faq.texi | 6 ------
tests/copycooker.sh | 4 ++--
2 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/doc/faq.texi b/doc/faq.texi
index 3daf44f..a29af1e 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -415,12 +415,6 @@ be rewritten in a formal object language. Further, many of
the developers
favor straight C; it works for them. For more arguments on this matter,
read "Programming Religion" at (@url{http://www.tux.org/lkml/#s15}).
-@section Why are the ffmpeg programs devoid of debugging symbols?
-
-The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
-information. Those binaries are stripped to create ffmpeg, ffplay, etc. If
-you need the debug information, use the *_g versions.
-
@section I do not like the LGPL, can I contribute code under the GPL instead?
Yes, as long as the code is optional and can easily and cleanly be placed
diff --git a/tests/copycooker.sh b/tests/copycooker.sh
index 4b5811d..3118e3f 100755
--- a/tests/copycooker.sh
+++ b/tests/copycooker.sh
@@ -13,8 +13,8 @@ rm -f $logfile
for i in $list ; do
echo ---------------- >> $logfile
echo $i >> $logfile
- ./ffmpeg_g -flags +bitexact -i $i -acodec copy -vcodec copy -y first.nut
- ./ffmpeg_g -flags +bitexact -i first.nut -acodec copy -vcodec copy -y
second.nut
+ ./ffmpeg -flags +bitexact -i $i -acodec copy -vcodec copy -y first.nut
+ ./ffmpeg -flags +bitexact -i first.nut -acodec copy -vcodec copy -y
second.nut
cmp first.nut second.nut >> $logfile
md5sum first.nut >> $logfile
done
--
1.5.6.5
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
