Bug 233978 – ffmpeg cannot be used to compile users sources due to an error in one of header files

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Paul Osmialowski 2008-08-05 13:33:59 UTC]

/usr/include/ffmpeg/avcodec.h has bugs that prevents users sources that depends on ffpmeg to be able to compile properly


Reproducible: Always

Steps to Reproduce:
1. emerge ffpmeg
2. download opencv or anything else that relies on ffpmeg
3. build opencv

Actual Results:  
booooo

Expected Results:  
succesful compilation

Proposed patch:

--- avcodec.h.old       2008-07-14 10:29:29.000000000 +0200
+++ avcodec.h   2008-08-05 13:01:34.112899770 +0200
@@ -26,7 +26,8 @@
  * external API header
  */

-
+#define __STDC_LIMIT_MACROS
+#include <stdint.h>
 #include "avutil.h"
 #include <sys/types.h> /* size_t */

@@ -39,7 +40,7 @@

 #define LIBAVCODEC_IDENT        "Lavc" AV_STRINGIFY(LIBAVCODEC_VERSION)

-#define AV_NOPTS_VALUE          INT64_C(0x8000000000000000)
+#define AV_NOPTS_VALUE          __INT64_C(0x8000000000000000)
 #define AV_TIME_BASE            1000000
 #define AV_TIME_BASE_Q          (AVRational){1, AV_TIME_BASE}

[Comment 1 Jeroen Roovers (RETIRED) 2008-08-05 16:45:45 UTC]

Have you seen bug #214740?

[Comment 2 Rafał Mużyło 2008-08-05 21:40:55 UTC]

Actually, it seems like he's complaining
about the old version, as this is 
libavcodec/avcodec.h.

[Comment 3 Paul Osmialowski 2008-08-06 08:03:51 UTC]

Well, I'm talking about the version that is stable on portage. If newer version differs only with header paths, this bug may still persist.

[Comment 4 Alexis Ballier 2008-08-07 08:31:44 UTC]

building c++ app, right ?
iirc you should define __STDC_CONSTANT_MACROS when using ffmpeg from c++ and that's what upstream wants you to do (or better: they don't care about c++ and that's the way it can work)

could you please try this ?

[Comment 5 Alexis Ballier 2008-08-25 10:49:29 UTC]

(In reply to comment #4)
> building c++ app, right ?
> iirc you should define __STDC_CONSTANT_MACROS when using ffmpeg from c++ and
> that's what upstream wants you to do (or better: they don't care about c++ and
> that's the way it can work)
> 
> could you please try this ?

no answer, setting as invalid; our opencv ebuild has a patch to fix this.