[FFmpeg-devel] compile issues under mingw-cross-env

Eli Friedman eli.friedman
Sat Jul 10 23:10:05 CEST 2010

On Sat, Jul 10, 2010 at 1:57 PM, Ramiro Polla <ramiro.polla at gmail.com> wrote:
> On Sat, Jul 10, 2010 at 5:53 PM, John Calcote <john.calcote at gmail.com> wrote:
>> On 7/10/2010 1:25 PM, M?ns Rullg?rd wrote:
>>> John Calcote <john.calcote at gmail.com> writes:
>>>> Anyone ever tried compiling ffmpeg under mingw-cross-env
>>>> (http://www.nongnu.org/mingw-cross-env/)? I've been playing with it and
>>>> I've found the following issues with CPPFLAGS in the generated config.mak:
>>>> 1) I had to change -std=c99 to -std=gnu99 because _STRICT_ANSI is
>>>> enabled if -std=c99 is used which means functions like strcasecmp aren't
>>>> available (at least the prototypes aren't).
>>> Wrong. ?strcasecmp() is part of C99 and on any conforming system is
>>> declared when using those flags.
>> I'm not seeing strcasecmp as being part of C99. I'm seeing it as being
>> part of POSIX 2001... Are you sure you're correct on this one? When I
>> google search strcasecmp and c99, I get very little information on the
>> pair. However, most of what I do get appear to be comments about how
>> ffmpeg doesn't compile under mingw.
> 'man standards' says:
> "POSIX.1-2001 is aligned with C99, so that all of the library
> functions standardised in C99 are also standardised in POSIX.1-1001."

strcasecmp is defined in strings.h, which is not part of C99.  So
-std=c99 vs. -std=gnu99 shouldn't have any affect.


More information about the ffmpeg-devel mailing list