From: xof <xof@skynet.be>
To: linux-media@vger.kernel.org
Subject: Re: VL4-DVB compilation issue not covered by Daily Automated
Date: Thu, 14 Jan 2010 18:27:54 +0100 [thread overview]
Message-ID: <4B4F541A.9040200@skynet.be> (raw)
In-Reply-To: <829197381001130744m24da5ea3xe1cb5135237b1127@mail.gmail.com>
Devin Heitmueller a écrit :
> On Wed, Jan 13, 2010 at 3:32 AM, xof <xof@skynet.be> wrote:
>
>> Are you sure? (it is an Ubuntu-only issue)
>>
>> I can see several
>>
>>> #include <asm/asm.h>
>>>
>> in the v4l tree that compile fine on Ubuntu
>> but only linux/drivers/media/dvb/firewire/firedtv-1394.c contains
>>
>>> #include <asm.h>
>>>
>> and doesn't compile.
>>
>> Unfortunately the asm.h asm/asm.h is not the only issue with
>> firedtv-1394.c (on Ubuntu/Karmic Koala?).
>> The /drivers/ieee1394/*.h seem to be in the linux-sources tree and not
>> in the linux-headers one (?)
>>
>> Everywhere I look, I read "don't bother, just disable firedtv-1394.c"
>> until they fix it.
>>
>
> I think perhaps you meant to write "dma.h" and not "asm.h".
>
> All of the missing includes in the error log (including "dma.h") are
> for files that are found in the iee1394 source directory, which are
> not provided in the Ubuntu linux-headers package.
>
> Devin
>
>
Oups! You are right...
Thank you.
xof
-------------------------
PS: I signaled the problem to the Ubuntu community
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/507154
I hope this was the right thing to do... I did not find any mention of
the problem there.
There is no reaction yet, it is just one of 5000 other things to look at...
prev parent reply other threads:[~2010-01-14 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 21:26 VL4-DVB compilation issue not covered by Daily Automated Hagen von Eitzen
2010-01-12 21:44 ` Devin Heitmueller
2010-01-13 8:32 ` xof
2010-01-13 15:44 ` Devin Heitmueller
2010-01-14 17:27 ` xof [this message]
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=4B4F541A.9040200@skynet.be \
--to=xof@skynet.be \
--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