From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: randconfig build error with next-20140826, in Documentation/video4linux
Date: Wed, 27 Aug 2014 10:25:38 -0700 [thread overview]
Message-ID: <53FE1492.10408@infradead.org> (raw)
In-Reply-To: <20140827141746.1ea8c11c.m.chehab@samsung.com>
On 08/27/14 10:17, Mauro Carvalho Chehab wrote:
> Em Wed, 27 Aug 2014 07:36:05 -0700
> Randy Dunlap <rdunlap@infradead.org> escreveu:
>
>> On 08/27/14 03:58, Sudip Mukherjee wrote:
>>> On Tue, Aug 26, 2014 at 09:50:43AM -0700, Jim Davis wrote:
>>>> Building with the attached random configuration file,
>>>>
>>>> ERROR: "vb2_ops_wait_finish"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ops_wait_prepare"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_event_unsubscribe"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_ctrl_subscribe_event"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_ctrl_log_status"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_streamoff"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_streamon"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_create_bufs"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_dqbuf"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_expbuf"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_qbuf"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_querybuf"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_ioctl_reqbufs"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_fop_release"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_fh_open" [Documentation/video4linux/v4l2-pci-skeleton.ko]
>>>> undefined!
>>>> ERROR: "vb2_fop_mmap" [Documentation/video4linux/v4l2-pci-skeleton.ko]
>>>> undefined!
>>>> ERROR: "video_ioctl2" [Documentation/video4linux/v4l2-pci-skeleton.ko]
>>>> undefined!
>>>> ERROR: "vb2_fop_poll" [Documentation/video4linux/v4l2-pci-skeleton.ko]
>>>> undefined!
>>>> ERROR: "vb2_fop_read" [Documentation/video4linux/v4l2-pci-skeleton.ko]
>>>> undefined!
>>>> ERROR: "vb2_buffer_done"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "__video_register_device"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "video_device_release_empty"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_dma_contig_init_ctx"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_queue_init"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_dma_contig_memops"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_ctrl_new_std"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_ctrl_handler_init_class"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_device_register"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_match_dv_timings"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_find_dv_timings_cap"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_valid_dv_timings"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_enum_dv_timings_cap"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "video_devdata"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_device_unregister"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "vb2_dma_contig_cleanup_ctx"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "v4l2_ctrl_handler_free"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> ERROR: "video_unregister_device"
>>>> [Documentation/video4linux/v4l2-pci-skeleton.ko] undefined!
>>>> make[1]: *** [__modpost] Error 1
>>>> make: *** [modules] Error 2
>>>>
>>>> Similar to a build error from January 7th:
>>>> https://lists.01.org/pipermail/kbuild-all/2014-January/002566.html
>>>
>>> Hi,
>>> I tried to build next-20140826 with your given config file . But for me everything was fine.
>>> And I was just wondering why the skeleton code in the Documentation is building ?
>>
>> It builds if the Kconfig symbol BUILD_DOCSRC is enabled.
>> Building of this module was just added to linux-next.
>
> It makes sense to add a depends on BUILD_DOCSRC, PCI and MEDIA_V4L2
> inside the docs Makefile, instead of moving the Kconfig to
> drivers/media, IMHO.
No, the dependencies should be in a Kconfig file, not in a Makefile.
If you insist, I'll look into moving the Kconfig contents into Documentation/.
--
~Randy
next prev parent reply other threads:[~2014-08-27 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 16:50 randconfig build error with next-20140826, in Documentation/video4linux Jim Davis
2014-08-27 10:58 ` Sudip Mukherjee
2014-08-27 14:36 ` Randy Dunlap
2014-08-27 17:17 ` Mauro Carvalho Chehab
2014-08-27 17:25 ` Randy Dunlap [this message]
2014-08-27 17:33 ` Jim Davis
2014-08-28 7:59 ` Sudip Mukherjee
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=53FE1492.10408@infradead.org \
--to=rdunlap@infradead.org \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).