From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: "Peter J. Olson" <peterjolson@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Compile error when I get to snd-go7007.c
Date: Mon, 14 Sep 2009 14:56:18 -0300 [thread overview]
Message-ID: <20090914145618.14e08573@pedra.chehab.org> (raw)
In-Reply-To: <64a476a80909141031u4e664a2ard4590988bf88de8f@mail.gmail.com>
Em Mon, 14 Sep 2009 12:31:28 -0500
"Peter J. Olson" <peterjolson@gmail.com> escreveu:
> Well, I made it a little farther... I think. I updated v4l-dvb: "hg
> pull" then updated "hg update"
>
> I then ran "make allmodconfig"
>
> This is my output:
> make -C /home/mythbox/Firmware/v4l-dvb/v4l allmodconfig
> make[1]: Entering directory `/home/mythbox/Firmware/v4l-dvb/v4l'
> ./scripts/make_kconfig.pl /lib/modules/2.6.28-15-generic/build
> /lib/modules/2.6.28-15-generic/build 1
> Preparing to compile for kernel version 2.6.28
>
> ***WARNING:*** You do not have the full kernel sources installed.
> This does not prevent you from building the v4l-dvb tree if you have the
> kernel headers, but the full kernel source may be required in order to use
> make menuconfig / xconfig / qconfig.
>
> If you are experiencing problems building the v4l-dvb tree, please try
> building against a vanilla kernel before reporting a bug.
>
> Vanilla kernels are available at http://kernel.org.
> On most distros, this will compile a newly downloaded kernel:
>
> cp /boot/config-`uname -r` <your kernel dir>/.config
> cd <your kernel dir>
> make all modules_install install
>
> Please see your distro's web site for instructions to build a new kernel.
>
> VIDEO_VPSS_SYSTEM: Requires at least kernel 2.6.31
> VIDEO_VPFE_CAPTURE: Requires at least kernel 2.6.31
> VIDEO_DM6446_CCDC: Requires at least kernel 2.6.31
> VIDEO_DM355_CCDC: Requires at least kernel 2.6.31
> VIDEO_PXA27x: Requires at least kernel 2.6.29
> VIDEO_CX25821: Requires at least kernel 2.6.31
> VIDEO_CX25821_ALSA: Requires at least kernel 2.6.31
> Created default (all yes) .config file
> ./scripts/fix_kconfig.pl
> make[1]: Leaving directory `/home/mythbox/Firmware/v4l-dvb/v4l'
>
> Then I made it here:
>
> CC [M] /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-core.o
> CC [M] /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-sg.o
> CC [M] /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.o
> /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.c: In function
> 'videobuf_dma_contig_user_get':
> /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.c:164: error:
> implicit declaration of function 'follow_pfn'
> make[3]: *** [/home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.o] Error 1
> make[2]: *** [_module_/home/mythbox/Firmware/v4l-dvb/v4l] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.28-15-generic'
> make[1]: *** [default] Error 2
> make[1]: Leaving directory `/home/mythbox/Firmware/v4l-dvb/v4l'
> make: *** [all] Error 2
>
> Its kinda annoying that a year ago this was super easy...
>
> I dont really want to bump up to 2.6.31 seeing it just came out a few days ago.
Ok, this is the usual backport issues we have every time we need to backport
patches upstream. This should be solved soon, but currently my priority is to
merge the pending patches at the tree. Up to then, you may do a:
make menuconfig
and select only the drivers you need, or just revert the latest changepatch to
videobuf-dma-config.
Cheers,
Mauro
prev parent reply other threads:[~2009-09-14 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 14:36 [linux-dvb] Compile error when I get to snd-go7007.c Peter J. Olson
[not found] ` <64a476a80909140739h6612ce69u2819335f7ea2c758@mail.gmail.com>
[not found] ` <64a476a80909140804s34ebd140r7934f46fb2150364@mail.gmail.com>
[not found] ` <64a476a80909140810j2c23a11fp994c6278ec01829a@mail.gmail.com>
2009-09-14 15:18 ` Peter J. Olson
2009-09-14 16:32 ` Mauro Carvalho Chehab
2009-09-14 17:31 ` Peter J. Olson
2009-09-14 17:56 ` Mauro Carvalho Chehab [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=20090914145618.14e08573@pedra.chehab.org \
--to=mchehab@infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=peterjolson@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox