From: kbuild test robot <fengguang.wu@intel.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Sasha Levin <sasha.levin@oracle.com>
Subject: undefined reference to `dib3000mc_pid_parse'
Date: Sat, 20 Feb 2016 19:49:18 +0800 [thread overview]
Message-ID: <201602201916.CBBTJt9R%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4099 bytes --]
Hi Kirill,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 020ecbba0548cefc91c3c5de32c28a62bcf37ed9
commit: 51b97e354ba9fce1890cf38ecc754aa49677fc89 kernel: use the gnu89 standard explicitly
date: 1 year, 3 months ago
config: x86_64-randconfig-b0-02201855 (attached as .config)
reproduce:
git checkout 51b97e354ba9fce1890cf38ecc754aa49677fc89
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `dvb_register':
cx23885-dvb.c:(.text+0x354e7c): undefined reference to `tda18271_attach'
drivers/built-in.o: In function `dibusb_dib3000mc_frontend_attach':
>> (.text+0x382239): undefined reference to `dib3000mc_pid_parse'
drivers/built-in.o: In function `dibusb_dib3000mc_frontend_attach':
>> (.text+0x382241): undefined reference to `dib3000mc_pid_control'
drivers/built-in.o: In function `dibusb_dib3000mc_tuner_attach':
(.text+0x382348): undefined reference to `dib3000mc_get_tuner_i2c_master'
drivers/built-in.o: In function `dibusb_dib3000mc_tuner_attach':
>> (.text+0x382447): undefined reference to `dib3000mc_set_config'
drivers/built-in.o: In function `dib90x0_tuner_sleep':
dib0700_devices.c:(.text+0x38af71): undefined reference to `dib9000_set_gpio'
drivers/built-in.o: In function `dib90x0_tuner_reset':
dib0700_devices.c:(.text+0x38af8a): undefined reference to `dib9000_set_gpio'
drivers/built-in.o: In function `stk9090m_frontend_attach':
dib0700_devices.c:(.text+0x38b11e): undefined reference to `dib9000_i2c_enumeration'
drivers/built-in.o: In function `nim9090md_frontend_attach':
dib0700_devices.c:(.text+0x38b425): undefined reference to `dib9000_i2c_enumeration'
dib0700_devices.c:(.text+0x38b4bd): undefined reference to `dib9000_get_i2c_master'
dib0700_devices.c:(.text+0x38b4d7): undefined reference to `dib9000_i2c_enumeration'
dib0700_devices.c:(.text+0x38b551): undefined reference to `dib9000_set_slave_frontend'
drivers/built-in.o: In function `dib90x0_pid_filter':
dib0700_devices.c:(.text+0x38b582): undefined reference to `dib9000_fw_pid_filter'
drivers/built-in.o: In function `dib90x0_pid_filter_ctrl':
dib0700_devices.c:(.text+0x38b598): undefined reference to `dib9000_fw_pid_filter_ctrl'
drivers/built-in.o: In function `bristol_tuner_attach':
dib0700_devices.c:(.text+0x38b5be): undefined reference to `dib3000mc_get_tuner_i2c_master'
drivers/built-in.o: In function `bristol_frontend_attach':
dib0700_devices.c:(.text+0x38b76c): undefined reference to `dib3000mc_i2c_enumeration'
drivers/built-in.o: In function `dib9090_tuner_attach':
dib0700_devices.c:(.text+0x38c08a): undefined reference to `dib9000_get_tuner_interface'
dib0700_devices.c:(.text+0x38c11b): undefined reference to `dib9000_get_i2c_master'
dib0700_devices.c:(.text+0x38c147): undefined reference to `dib9000_firmware_post_pll_init'
drivers/built-in.o: In function `nim9090md_tuner_attach':
dib0700_devices.c:(.text+0x38c1a1): undefined reference to `dib9000_get_tuner_interface'
dib0700_devices.c:(.text+0x38c217): undefined reference to `dib9000_get_i2c_master'
dib0700_devices.c:(.text+0x38c244): undefined reference to `dib9000_firmware_post_pll_init'
dib0700_devices.c:(.text+0x38c25d): undefined reference to `dib9000_get_slave_frontend'
dib0700_devices.c:(.text+0x38c275): undefined reference to `dib9000_get_component_bus_interface'
dib0700_devices.c:(.text+0x38c280): undefined reference to `dib9000_set_i2c_adapter'
dib0700_devices.c:(.text+0x38c288): undefined reference to `dib9000_get_tuner_interface'
dib0700_devices.c:(.text+0x38c30d): undefined reference to `dib9000_fw_set_component_bus_speed'
dib0700_devices.c:(.text+0x38c315): undefined reference to `dib9000_firmware_post_pll_init'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 24635 bytes --]
next reply other threads:[~2016-02-20 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 11:49 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-28 8:15 kbuild test robot
2015-12-08 4:30 kbuild test robot
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=201602201916.CBBTJt9R%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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
all inboxes | Powered by JetHome®