From: Jean-Francois Moine <moinejf@free.fr>
To: video4linux-list@redhat.com
Subject: compilation errors
Date: Tue, 01 Jul 2008 13:21:36 +0200 [thread overview]
Message-ID: <1214911296.1699.18.camel@localhost> (raw)
Hi all,
There should be something I missed in the linuxtv documents.
When I do a simple 'make', in v4l, it generates almost all the .ko files
of the modules of the first level. But I cannot find, for example, any
v4l2-common.ko, nor tuner-simple.ko.
Then, I linked by hand the tree to my kernel (2.6.26-rc8). I thought
some links only were needed, so I linked:
drivers/media
include/media
include/linux/videodev2.h
A 'make' in the kernel tree stops with many warnings and errors, mainly:
warning: "LINUX_VERSION_CODE" is not defined
Any hint? Thank you.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-07-01 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 11:21 Jean-Francois Moine [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 9:35 Compilation errors Fabio M. De Francesco
2022-04-01 10:13 ` Stefano Brivio
2022-04-01 12:01 ` Fabio M. De Francesco
2022-04-01 12:57 ` Stefano Brivio
2022-04-01 13:07 ` Fabio M. De Francesco
2022-04-01 16:09 ` Alison Schofield
2022-04-01 17:58 ` Fabio M. De Francesco
2022-04-01 14:39 ` Fabio M. De Francesco
2008-02-05 2:59 Peter Teoh
1999-02-03 14:31 Richard Hartensveld
1999-02-03 17:12 ` Alex deVries
1999-02-03 20:43 ` Ulf Carlsson
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=1214911296.1699.18.camel@localhost \
--to=moinejf@free.fr \
--cc=video4linux-list@redhat.com \
/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.