From: kbuild test robot <fengguang.wu@intel.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Jonas Bonn <jonas@southpole.se>
Subject: vgacon.c:undefined reference to `screen_info'
Date: Sun, 2 Oct 2016 09:42:52 +0800 [thread overview]
Message-ID: <201610020941.ADFrIlWs%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
Hi Chen,
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: f51fdffad5b7709d0ade40736b58a2da2707fa15
commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm: Kbuild: add default "vga.h"
date: 2 years, 11 months ago
config: openrisc-alldefconfig (attached as .config)
compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout f69405ce6c0fc9f4a039011007371b31f80b470d
# save the attached .config to linux build tree
make.cross ARCH=openrisc
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `vgacon_save_screen':
>> vgacon.c:(.text+0x20e0): undefined reference to `screen_info'
vgacon.c:(.text+0x20e8): undefined reference to `screen_info'
drivers/built-in.o: In function `vgacon_init':
vgacon.c:(.text+0x284c): undefined reference to `screen_info'
vgacon.c:(.text+0x2850): undefined reference to `screen_info'
drivers/built-in.o: In function `vgacon_startup':
vgacon.c:(.text+0x28d8): undefined reference to `screen_info'
drivers/built-in.o:vgacon.c:(.text+0x28f0): more undefined references to `screen_info' follow
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 5151 bytes --]
next reply other threads:[~2016-10-02 1:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 1:42 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-20 8:06 vgacon.c:undefined reference to `screen_info' kbuild test robot
2016-11-13 10:06 kbuild test robot
2016-10-31 3:46 kbuild test robot
2016-10-23 8:46 kbuild test robot
2016-10-16 11:04 kbuild test robot
2016-09-22 22:07 kbuild test robot
2016-09-05 0:57 kbuild test robot
2016-08-23 12:07 kbuild test robot
2016-08-07 1:43 kbuild test robot
2016-07-31 1:20 kbuild test robot
2016-07-17 0:51 kbuild test robot
2016-07-07 7:52 kbuild test robot
2016-06-26 4:54 kbuild test robot
2016-06-12 22:16 kbuild test robot
2016-06-12 18:40 kbuild test robot
2016-06-05 5:31 kbuild test robot
2016-04-18 4:12 kbuild test robot
2016-03-22 0:50 kbuild test robot
2016-03-13 16:10 kbuild test robot
2016-03-06 1:00 kbuild test robot
2016-02-28 21:41 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=201610020941.ADFrIlWs%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=gang.chen@asianux.com \
--cc=jonas@southpole.se \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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).