[FFmpeg-cvslog] r14769 - trunk/configure

[Måns Rullgård]

Stefano Sabatini wrote:
> On date Tuesday 2008-08-19 12:53:04 +0200, Stefano Sabatini wrote:
>> On date Tuesday 2008-08-19 00:13:39 +0100, M?ns Rullg?rd wrote:
>> > Luca Abeni <lucabe72 at email.it> writes:
>> >
>> > > On Tue, 2008-08-19 at 00:51 +0200, Luca Abeni wrote:
>> > >> Hi M?ns,
>> > >>
>> > >> M?ns Rullg?rd wrote:
>> > >> [...]
>> > >> >> I'll try to test some older version of debian later...
>> > >> >
>> > >> > We've already confirmed broken headers on some version of Ubuntu
>> > >> > causing this problem.  I reckon it's the same thing here.
>> > >>
>> > >> Ah, ok; I did not know this. Sorry for the noise, then.
>> > >
>> > > Sorry, just another question about this issue: shouldn't the configure
>> > > script detect the broken videodev2 header and disable v4l2.c
>> > > compilation?
>> > >
>> > > I mean: according to Stefano's log, the compilation fails when including
>> > > linux/videodev2.h. The configure script tries to compile a simple
>> > > program including this header, and should disable v4l2 if this
>> > > compilation fails. So, I am wondering why the build system is trying to
>> > > compile v4l2.c... What am I missing?
>> >
>> > I'd have to see the configure log to answer that.
>>
>> I'm appending it (compressed).
>
> [...]
> The compilation doesnt' fail because of the -E flag, it reports
> success if the preprocessing was successfull, but doesn't try to
> actually compile it. From the gcc man page:
>
>     -E  Stop after the preprocessing stage; do not run the compiler proper.
>            The output is in the form of preprocessed source code, which is
>            sent to the standard output.
>
>            Input files which don?t require preprocessing are ignored.
>
> I wonder if this is a limit of the configure system.

It's a feature.  See my other mail.

> BTW can someone suggest which linux headers work after the std=c99
> change (who suggest to use a newer, who an older version), if the
> problem is upstream we should report it.

The headers are fine in Linux git.  I'm didn't check since when.
Apparenly distros have been patching the installed headers for
some time, with varying degree of success.

-- 
M?ns Rullg?rd
mans at mansr.com