From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>,
Andy Walls <awalls@md.metrocast.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Media_build does not compile due to errors in cx18-driver.h, cx18-driver.c and dvbdev.c /rc-main.c
Date: Fri, 10 Jun 2011 15:22:47 +0200 [thread overview]
Message-ID: <4DF21AA7.1010505@hoogenraad.net> (raw)
In-Reply-To: <BANLkTinE1vRVJ+j+7JiPHZqXHJ8WTFX+cg@mail.gmail.com>
Andy:
Something along the line of id already defined.
I just corrected the code by removing the duplicate lines that are in
the sources of the tar.
The other 3 files have a bad escape sequence in a line saying that this
is the backports. One backslash not removed in a script, I guess.
Devin:
The version does not matter for the cx18 problem: any compiler complains
on duplicate lines.
Anyway: 2.6.32-32-generic-pae #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC
2011 i686 GNU/Linux
Devin Heitmueller wrote:
> On Fri, Jun 10, 2011 at 8:34 AM, Andy Walls<awalls@md.metrocast.net> wrote:
>> What are the error messages?
>>
>> Tejun Heo made quite a number of workqueue changes, and the cx18 driver got dragged forward with them. So did ivtv for that matter.
>>
>> Just disable the cx18 driver if you don't need it for an older kernel.
>>
>> Regards,
>> Andy
>
> Another highly relevant piece of information to know is what kernel
> Jan is running on. It is probably from before the workqueue changes.
>
> Devin
>
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
next prev parent reply other threads:[~2011-06-10 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 11:24 Media_build does not compile due to errors in cx18-driver.h, cx18-driver.c and dvbdev.c /rc-main.c Jan Hoogenraad
2011-06-10 12:34 ` Andy Walls
2011-06-10 13:12 ` Devin Heitmueller
2011-06-10 13:22 ` Jan Hoogenraad [this message]
2011-06-10 14:14 ` Jan Hoogenraad
2011-06-10 15:34 ` Mauro Carvalho Chehab
2011-06-10 16:07 ` Mauro Carvalho Chehab
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=4DF21AA7.1010505@hoogenraad.net \
--to=jan-conceptronic@hoogenraad.net \
--cc=awalls@md.metrocast.net \
--cc=dheitmueller@kernellabs.com \
--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