From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: linux-media@vger.kernel.org
Subject: Build LinuxTV on Raspbian?
Date: Sun, 10 May 2015 19:21:49 +0200 [thread overview]
Message-ID: <201505101921.49294.Dexter.Filmore@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
On Raspbian/wheezy with 3.18.7 kernel I ran the basic approach and end up
somewhere here:
...
v4l-cx231xx-avcore-01.fw
v4l-cx23418-apu.fw
v4l-cx23418-cpu.fw
v4l-cx23418-dig.fw
v4l-cx23885-avcore-01.fw
v4l-cx23885-enc-broken.fw
v4l-cx25840.fw
******************
* Start building *
******************
make -C /home/pi/media_build/v4l allyesconfig
make[1]: Entering directory '/home/pi/media_build/v4l'
make[2]: Entering directory '/home/pi/media_build/linux'
Applying patches for kernel 3.18.7-v7+
patch -s -f -N -p1 -i ../backports/api_version.patch
patch -s -f -N -p1 -i ../backports/pr_fmt.patch
patch -s -f -N -p1 -i ../backports/debug.patch
patch -s -f -N -p1 -i ../backports/drx39xxj.patch
patch -s -f -N -p1 -i ../backports/v4.0_dma_buf_export.patch
patch -s -f -N -p1 -i ../backports/v4.0_drop_trace.patch
Patched drivers/media/dvb-core/dvbdev.c
Patched drivers/media/v4l2-core/v4l2-dev.c
Patched drivers/media/rc/rc-main.c
make[2]: Leaving directory '/home/pi/media_build/linux'
./scripts/make_kconfig.pl /lib/modules/3.18.7-v7+/build /lib/modules/3.18.7-v7+/build
1
Preparing to compile for kernel version 3.18.7
File not found: /lib/modules/3.18.7-v7+/build/.config
at ./scripts/make_kconfig.pl line 33, <IN> line 4.
Makefile:366: recipe for target 'allyesconfig' failed
make[1]: *** [allyesconfig] Error 2
make[1]: Leaving directory '/home/pi/media_build/v4l'
Makefile:26: recipe for target 'allyesconfig' failed
make: *** [allyesconfig] Error 2
can't select all drivers at ./build line 490.
I am clueless what goes wrong, pointers appreciated.
A generic google search regarding kernel module compiles on RasPis
points some kernel config files are not in place where they should be,
but I don't know how to tackle the issue.
Dex
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2015-05-10 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201505101921.49294.Dexter.Filmore@gmx.de \
--to=dexter.filmore@gmx.de \
--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