All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ole W. Saastad" <olewsaa@online.no>
To: linux-media@vger.kernel.org
Subject: Trouble building v4l-dvb
Date: Tue, 14 Sep 2010 21:38:29 +0200	[thread overview]
Message-ID: <1284493110.1801.57.camel@sofia> (raw)

Trouble building v4l-dvb
Asus eee netbook, running EasyPeasy.

ole@ole-eee:~$ cat /etc/issue
Ubuntu 9.04 \n \l
ole@ole-eee:~$ uname -a
Linux ole-eee 2.6.30.5-ep0 #10 SMP PREEMPT Thu Aug 27 19:45:06 CEST 2009
i686 GNU/Linux

Rationale for building from source: 
I have bought a USB TV with mpg4 support from Sandberg, Mini DVB-T
dongle. I also received an archive with driver routines for this from
Sandberg. These should be copied into the v4l-dvd three and just rebuild
with make. 

I have installed the kernel headers:
apt-get install mercurial linux-headers-$(uname -r) build-essential

Then I have downloaded the v4l-dvb source (assuming this is a stable
release): hg clone http://linuxtv.org/hg/v4l-dvb


I wanted to try to build before applying the patch from Sandberg. 
Issuing make yield the following :

LIRC: Requires at least kernel 2.6.36
IR_LIRC_CODEC: Requires at least kernel 2.6.36
IR_IMON: Requires at least kernel 2.6.36
IR_MCEUSB: Requires at least kernel 2.6.36
VIDEOBUF_DMA_CONTIG: Requires at least kernel 2.6.31
V4L2_MEM2MEM_DEV: Requires at least kernel 2.6.33
and a few more lines....

Ignoring these and just continuing :

  CC [M]  /home/ole/work/v4l-dvb/v4l/firedtv-dvb.o
  CC [M]  /home/ole/work/v4l-dvb/v4l/firedtv-fe.o
  CC [M]  /home/ole/work/v4l-dvb/v4l/firedtv-1394.o
/home/ole/work/v4l-dvb/v4l/firedtv-1394.c:22:17: error: dma.h: No such
file or directory
/home/ole/work/v4l-dvb/v4l/firedtv-1394.c:23:21: error: csr1212.h: No
such file or directory
/home/ole/work/v4l-dvb/v4l/firedtv-1394.c:24:23: error: highlevel.h: No
such file or directory
and many many more similar errors.

After some time the make bails out.


I assume this have some connection with the 9.04 being too old. 


Hints ?



Regards,
Ole W. Saastad





             reply	other threads:[~2010-09-14 20:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 19:38 Ole W. Saastad [this message]
2010-09-16 17:07 ` Trouble building v4l-dvb Jan Hoogenraad
2010-09-17  9:35   ` Jan Hoogenraad
2010-09-17 10:50     ` Mauro Carvalho Chehab
2010-09-17 11:08       ` Jan Hoogenraad
2010-09-17 14:49         ` Mauro Carvalho Chehab
2010-09-17 15:00           ` Devin Heitmueller
2010-09-17 15:08             ` Mauro Carvalho Chehab
2010-09-17 15:27           ` Jan Hoogenraad
2010-09-26 16:18           ` Jan Hoogenraad
2010-09-27  4:08             ` Mauro Carvalho Chehab
2010-09-27 18:41               ` updated make_kconfig.pl for Ubuntu Jan Hoogenraad
2010-09-27 19:12                 ` Mauro Carvalho Chehab
2010-09-27 20:45                   ` Jan Hoogenraad
2010-09-27 22:43                     ` Mauro Carvalho Chehab
2010-09-28 17:48                       ` Jan Hoogenraad
2010-09-28 18:21                         ` Mauro Carvalho Chehab
2010-09-28 19:58                           ` Jan Hoogenraad
2010-09-29 21:49                           ` patches for the Realtek rtl2831 Jan Hoogenraad
2010-09-17 17:33     ` Trouble building v4l-dvb Ole W. Saastad
2010-09-17 17:58       ` rtl2832 chip driver Jan Hoogenraad

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=1284493110.1801.57.camel@sofia \
    --to=olewsaa@online.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.