From e867d9b9c0291335c1e78c0240f097cf97a64cfd Mon Sep 17 00:00:00 2001
From: Diego Biurrun <diego@biurrun.de>
Date: Thu, 25 Jan 2007 17:34:08 +0000
Subject: [PATCH] Update gcc sections.

Originally committed as revision 7712 to svn://svn.ffmpeg.org/ffmpeg/trunk
---
 doc/faq.texi | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/doc/faq.texi b/doc/faq.texi
index 95951c16b82..b048e18ae0a 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -257,9 +257,9 @@ already incorporate ffmpeg at (@url{projects.php}).
 
 @section Can you support my C compiler XXX ?
 
-No. Only GCC is supported. GCC is ported to most systems available and there
-is no need to pollute the source code with @code{#ifdef}s
-related to the compiler.
+It depends. If your compiler is C99-compliant, then patches to support
+it are likely to be welcome if they do not pollute the source code
+with @code{#ifdef}s related to the compiler.
 
 @section Can I use FFmpeg or libavcodec under Windows ?
 
@@ -270,9 +270,7 @@ sections in the FFmpeg documentation to find more information.
 
 @section Can you add automake, libtool or autoconf support ?
 
-No. These tools are too bloated and they complicate the build. Moreover,
-since only @samp{gcc} is supported they would add little advantages in
-terms of portability.
+No. These tools are too bloated and they complicate the build.
 
 @section Why not rewrite ffmpeg in object-oriented C++ ?
 
-- 
GitLab