public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kernen <tkernen@deckpoint.ch>
To: linux-media@vger.kernel.org
Subject: Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)
Date: Wed, 11 Nov 2009 16:54:49 +0100	[thread overview]
Message-ID: <4AFADE49.9070600@deckpoint.ch> (raw)
In-Reply-To: <4AF9150D.2070601@deckpoint.ch>

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

  reply	other threads:[~2009-11-11 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  7:23 v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors) Thomas Kernen
2009-11-11 15:54 ` Thomas Kernen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-19 14:52 Devin Heitmueller
2009-06-19 15:33 ` Hans Verkuil
2009-06-19 15:42   ` Devin Heitmueller
2009-06-19 16:04     ` Hans Verkuil
2009-06-19 16:11       ` Devin Heitmueller
2009-06-19 16:41         ` Hans Verkuil
2009-06-21  0:52           ` Devin Heitmueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AFADE49.9070600@deckpoint.ch \
    --to=tkernen@deckpoint.ch \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox