[Ffmpeg-devel] question on qt-faststart.c

[Benoit Fouet]

Hi,

Diego Biurrun wrote:
> On Mon, Mar 12, 2007 at 09:01:26AM +0100, Benoit Fouet wrote:
>   
>> Mike Melanson wrote:
>>     
>>> Benoit Fouet wrote:
>>>       
>>>> Mike Melanson wrote:
>>>>         
>>>>> Benoit Fouet wrote:
>>>>>           
>>>>>> well, this will be short, when compilling it on my machine at work
>>>>>> (AMD64), i got warning about fseeko and got a program file that didn't
>>>>>> work (infinite reading file loop)...
>>>>>> compiling it here at home on my Celeron, it works just fine...
>>>>>> in addition, defining fseeko to fseek on my AMD made it work
>>>>>> Just wanted to know, out of curiosity, if someone here can explain
>>>>>> to me
>>>>>> where the problem is.
>>>>>>             
>>>>> What glibc version?
>>>>>
>>>>>           
>>>> I'll have to check that on monday, i can tell for sure...
>>>> i'll tell you then.
>>>>         
>>> While you're at it, don't forget to mention what the exact
>>> compile-time warning was regarding fseeko.
>>>
>>> The reason I asked about glibc version is that the man page for fseeko
>>> says it wasn't introduced until later. However, if it's not available
>>> on your system, the program shouldn't have compiled in the first place.
>>>
>>>       
>> OK, what i have is:
>>  - libc version: 2.3.6
>>  - command and output warnings:
>> $ gcc -Wall qt-faststart.c -o qt-faststart
>> qt-faststart.c: In function `main':
>> qt-faststart.c:133: warning: implicit declaration of function `fseeko'
>> qt-faststart.c:140: warning: implicit declaration of function `ftello'
>>     
>
> You don't have fseeko and ftello in /usr/include/stdio.h?
>   
i have a definition of fseeko only if:
#if defined __USE_LARGEFILE || defined __USE_XOPEN2K
it can be either:
extern int fseeko (FILE *__stream, __off_t __off, int __whence);
or:
extern int __REDIRECT (fseeko,
               (FILE *__stream, __off64_t __off, int __whence),
               fseeko64);
or:
#   define fseeko fseeko64

and a definition of fseeko64 only if:
#ifdef __USE_LARGEFILE64


it seems i don't reach any of those definition...

Ben