From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Martin Burnicki <martin.burnicki@burnicki.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Current media_build doesn't succeed building on kernel 3.1.10
Date: Mon, 1 Oct 2012 11:02:41 -0300 [thread overview]
Message-ID: <20121001110241.2f5ab052@redhat.com> (raw)
In-Reply-To: <201209302052.42723.martin.burnicki@burnicki.net>
Em Sun, 30 Sep 2012 20:52:42 +0200
Martin Burnicki <martin.burnicki@burnicki.net> escreveu:
> Hi all,
>
> is anybody out there who can help me with the media_build system? I'm trying
> to build the current modules on an openSUSE 12.1 system (kernel 3.1.10,
> x86_64), but I'm getting compilation errors because the s5k4ecgx driver uses
> function devm_regulator_bulk_get() which AFAICS has been introduced in kernel
> 3.4 only. When I run the ./build script compilation stops with these
> messages:
>
> CC [M] /root/projects/media_build/v4l/s5k4ecgx.o
> media_build/v4l/s5k4ecgx.c: In function 's5k4ecgx_load_firmware':
> media_build/v4l/s5k4ecgx.c:346:2: warning: format '%d' expects argument of \
> type 'int', but argument 4 has type 'size_t' [-Wformat]
> media_build/v4l/s5k4ecgx.c: In function 's5k4ecgx_probe':
> media_build/v4l/s5k4ecgx.c:977:2: error: implicit declaration of \
> function 'devm_regulator_bulk_get' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
Those are warnings. It wil compile if you disable -Werror=implicit-function-declaration.
>
>
> Probably I'll don't need module s5k4ecgx anyway, so any hint how to exclude
> this from build would be fine.
>
> On this page
> http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers#Retrieving_and_Building.2FCompiling_the_Latest_V4L-DVB_Source_Code
> the section "More Manually Intensive Approach" mentions steps where I can
> run "make menuconfig" after unpacking the sources and before the build
> process is started, so I could deselect the module(s) I don't need and
> exclude them from build. However, I've no idea what I should use for "DIR="
> in the command
>
> make tar DIR=<some dir with media -git tree>
>
> mentioned on the web page.
>
> According to theis link
> https://patchwork.kernel.org/patch/1267511/
> the s5k4ecgx module which does not build here has just been added at the
> beginning of August, so if I could specify a git version of the code which is
> slightly older this might also work.
>
> BTW, if I understand the build environment correctly then there should be
> dayly test builds of the package for varions kernels. I'd expect those
> automated builds should also fail for kernels older than 3.4.
>
>
> Regards,
>
> Martin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Mauro
next prev parent reply other threads:[~2012-10-01 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 18:52 Current media_build doesn't succeed building on kernel 3.1.10 Martin Burnicki
2012-10-01 14:02 ` Mauro Carvalho Chehab [this message]
2012-10-01 19:31 ` Martin Burnicki
2012-10-01 19:39 ` Mauro Carvalho Chehab
2012-10-02 1:30 ` Michael West
2012-10-02 10:42 ` Michael West
2012-10-02 10:49 ` Hans Verkuil
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=20121001110241.2f5ab052@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=martin.burnicki@burnicki.net \
/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.