From: Hans Verkuil <hverkuil@xs4all.nl>
To: Isaac Nickaein <nickaein.i@gmail.com>, linux-media@vger.kernel.org
Subject: Re: "error: redefinition of 'altera_init'" during build on Kernel 3.0.36+
Date: Sun, 27 Jul 2014 09:53:55 +0200 [thread overview]
Message-ID: <53D4B013.2060404@xs4all.nl> (raw)
In-Reply-To: <CA+NJmkcTpf5Xb4Z8gJFriB58Jtf85ay_jnTS-fM34gA1PBf60g@mail.gmail.com>
On 07/27/2014 08:47 AM, Isaac Nickaein wrote:
> Hello,
>
> I get the following error when I try to build the V4L2 on Kernel
> 3.0.36+ for ARM architecture:
>
> /root/v4l2/media_build/v4l/altera.c:2417:5: error: redefinition of 'altera_init'
> int altera_init(struct altera_config *config, const struct firmware *fw)
> ^
> In file included from /root/v4l2/media_build/v4l/altera.c:32:0:
> /root/v4l2/media_build/v4l/../linux/include/misc/altera.h:41:19: note:
> previous definition of 'altera_init' was here
> static inline int altera_init(struct altera_config *config,
> ^
>
>
> I checked the altera.h code and apparently, the IS_ENABLED macro is
> not defined and causes this problem. I have prepared kernel source at
> /lib/modules/3.0.36+/build/ and it builds successfully.
>
> Can anyone help me on this issue?
What kernel tree are you using? There is no IS_ENABLED in 3.0, so apparently
you have a patched kernel. Do you actually need that altera driver? If not,
then why not disable it in the kernel config?
Regards,
Hans
next prev parent reply other threads:[~2014-07-27 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 6:47 "error: redefinition of 'altera_init'" during build on Kernel 3.0.36+ Isaac Nickaein
2014-07-27 7:53 ` Hans Verkuil [this message]
2014-07-27 8:18 ` Isaac Nickaein
2014-07-27 8:26 ` Hans Verkuil
2014-07-27 8:42 ` Isaac Nickaein
2014-07-27 9:00 ` Hans Verkuil
2014-07-27 9:36 ` Isaac Nickaein
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=53D4B013.2060404@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=nickaein.i@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