Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Thomas Kernen]

Hello,

I came across this thread from June 2009 in the news archives about 
Ubuntu Karmic and v4l-dvb compile broken with stock Ubuntu Karmic build:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/7161

I've just come across this issue myself after an upgrade of a server to 
the Ubuntu Karmic release.

Is there any plans to attempt to mitigate this so that other users would 
not be impacted?

Regards,
Thomas

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Thomas Kernen]

Thomas Kernen wrote:
> Hello,
> 
> I came across this thread from June 2009 in the news archives about 
> Ubuntu Karmic and v4l-dvb compile broken with stock Ubuntu Karmic build:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/7161 
> 
> 
> I've just come across this issue myself after an upgrade of a server to 
> the Ubuntu Karmic release.
> 
> Is there any plans to attempt to mitigate this so that other users would 
> not be impacted?
> 
> Regards,
> Thomas

I don't like answering my own messages but hopefully this will be useful 
to other users too who may come across the same issue as I and didn't do 
enough research before asking the question.

Ubuntu Karmic is missing some Firewire/IEEE1394 files in the 
kernel-headers package.

Workaround:
in the v4l folder, open the .config file, find the line with 
"CONFIG_DVB_FIREDTV=m" and change to "CONFIG_DVB_FIREDTV=n".

Thomas

v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Devin Heitmueller]

It seems that attempting to compile the current v4l-dvb against a
stock Karmic Koala build fails.  I suspect this has to do with the
fact that 2.6.30 is built with ieee1394 enabled, which causes
firedtv-ieee1394.c to get compiled, and that file references #include
files that do not exist.  As far as I can tell, IEEE1394 is not
enabled in my 2.6.27 build, which is why I was not seeing it before.

Other users reported this issue on the #linuxtv irc a few days ago,
and I though it was just something weird about their environment.

I'm not familiar with the firedtv driver, so if someone who is wants
to chime in, I would appreciate it.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Hans Verkuil]

On Friday 19 June 2009 16:52:06 Devin Heitmueller wrote:
> It seems that attempting to compile the current v4l-dvb against a
> stock Karmic Koala build fails.  I suspect this has to do with the
> fact that 2.6.30 is built with ieee1394 enabled, which causes
> firedtv-ieee1394.c to get compiled, and that file references #include
> files that do not exist.  As far as I can tell, IEEE1394 is not
> enabled in my 2.6.27 build, which is why I was not seeing it before.
>
> Other users reported this issue on the #linuxtv irc a few days ago,
> and I though it was just something weird about their environment.
>
> I'm not familiar with the firedtv driver, so if someone who is wants
> to chime in, I would appreciate it.
>
> Devin

What's the compile error exactly? The firedtv driver compiles fine in the 
daily build against the vanilla 2.6.30 kernel.

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Devin Heitmueller]

On Fri, Jun 19, 2009 at 11:33 AM, Hans Verkuil<hverkuil@xs4all.nl> wrote:
> What's the compile error exactly? The firedtv driver compiles fine in the
> daily build against the vanilla 2.6.30 kernel.
>
> Regards,
>
>        Hans
>

Unfortunately, I sent the email from work and didn't have the output
in front of me (or else I would have pasted it into the email).
Several people also reported it on #linuxtv on 6/11, but it looks like
the pastebins have already expired.  :-(

I will provide the output tonight.  I started to debug it last night,
and it seems that firedtv-ieee1494.c doesn't normally get compiled at
all, so if you add 1394 support to your build you will likely also see
the issue.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Hans Verkuil]

On Friday 19 June 2009 17:42:18 Devin Heitmueller wrote:
> On Fri, Jun 19, 2009 at 11:33 AM, Hans Verkuil<hverkuil@xs4all.nl> wrote:
> > What's the compile error exactly? The firedtv driver compiles fine in
> > the daily build against the vanilla 2.6.30 kernel.
> >
> > Regards,
> >
> >        Hans
>
> Unfortunately, I sent the email from work and didn't have the output
> in front of me (or else I would have pasted it into the email).
> Several people also reported it on #linuxtv on 6/11, but it looks like
> the pastebins have already expired.  :-(
>
> I will provide the output tonight.  I started to debug it last night,
> and it seems that firedtv-ieee1494.c doesn't normally get compiled at
> all, so if you add 1394 support to your build you will likely also see
> the issue.

Hmm, I discovered that firedtv-1394.c isn't compiled in the daily build even 
though ieee1394 is enabled in the kernel. I can manually enable it, though: 
make menuconfig, disable and enable the firedtv driver, and then it 
magically works. But even then it still compiles fine against the vanilla 
2.6.30 kernel.

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Devin Heitmueller]

On Fri, Jun 19, 2009 at 12:04 PM, Hans Verkuil<hverkuil@xs4all.nl> wrote:
> Hmm, I discovered that firedtv-1394.c isn't compiled in the daily build even
> though ieee1394 is enabled in the kernel. I can manually enable it, though:
> make menuconfig, disable and enable the firedtv driver, and then it
> magically works. But even then it still compiles fine against the vanilla
> 2.6.30 kernel.

Well, I'm obviously kicking myself for not having captured the output
last night when I was at home.

So, you're saying that firedvt-1394.c is being compiled?

Let me rephrase the question:  Take a look at firedtv-1394.c, line 22,
and tell me where the file "csr1212.h" can be found either in your
kernel source tree or your v4l-dvb tree.

Devin


-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Hans Verkuil]

On Friday 19 June 2009 18:11:11 Devin Heitmueller wrote:
> On Fri, Jun 19, 2009 at 12:04 PM, Hans Verkuil<hverkuil@xs4all.nl> wrote:
> > Hmm, I discovered that firedtv-1394.c isn't compiled in the daily build
> > even though ieee1394 is enabled in the kernel. I can manually enable
> > it, though: make menuconfig, disable and enable the firedtv driver, and
> > then it magically works. But even then it still compiles fine against
> > the vanilla 2.6.30 kernel.
>
> Well, I'm obviously kicking myself for not having captured the output
> last night when I was at home.
>
> So, you're saying that firedvt-1394.c is being compiled?
>
> Let me rephrase the question:  Take a look at firedtv-1394.c, line 22,
> and tell me where the file "csr1212.h" can be found either in your
> kernel source tree or your v4l-dvb tree.
>
> Devin

It's here:

/usr/src/linux/drivers/ieee1394/csr1212.h

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)

[Devin Heitmueller]

On Fri, Jun 19, 2009 at 12:41 PM, Hans Verkuil<hverkuil@xs4all.nl> wrote:
> On Friday 19 June 2009 18:11:11 Devin Heitmueller wrote:
>> On Fri, Jun 19, 2009 at 12:04 PM, Hans Verkuil<hverkuil@xs4all.nl> wrote:
>> > Hmm, I discovered that firedtv-1394.c isn't compiled in the daily build
>> > even though ieee1394 is enabled in the kernel. I can manually enable
>> > it, though: make menuconfig, disable and enable the firedtv driver, and
>> > then it magically works. But even then it still compiles fine against
>> > the vanilla 2.6.30 kernel.
>>
>> Well, I'm obviously kicking myself for not having captured the output
>> last night when I was at home.
>>
>> So, you're saying that firedvt-1394.c is being compiled?
>>
>> Let me rephrase the question:  Take a look at firedtv-1394.c, line 22,
>> and tell me where the file "csr1212.h" can be found either in your
>> kernel source tree or your v4l-dvb tree.
>>
>> Devin
>
> It's here:
>
> /usr/src/linux/drivers/ieee1394/csr1212.h
>
> Regards,
>
>        Hans
>
> --
> Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
>

Ok, I see what is going on:  the header files in question are
available if you have the full Linux source installed, but they are
not part of the "kernel-headers" package, at least on Ubuntu.
Combined with the fact that the file now gets built with 2.6.30 causes
the compile failures:

  CC [M]  /home/devin/800e_test/v4l/firedtv-1394.o
/home/devin/800e_test/v4l/firedtv-1394.c:21:17: error: dma.h: No such
file or directory
/home/devin/800e_test/v4l/firedtv-1394.c:22:21: error: csr1212.h: No
such file or directory
/home/devin/800e_test/v4l/firedtv-1394.c:23:23: error: highlevel.h: No
such file or directory
/home/devin/800e_test/v4l/firedtv-1394.c:24:19: error: hosts.h: No
such file or directory
/home/devin/800e_test/v4l/firedtv-1394.c:25:22: error: ieee1394.h: No
such file or directory
/home/devin/800e_test/v4l/firedtv-1394.c:26:17: error: iso.h: No such
file or directory
/home/devin/800e_test/v4l/firedtv-1394.c:27:21: error: nodemgr.h: No
such file or directory

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com