From: Joe Perches <joe@perches.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: undefined reference to `printk'
Date: Sat, 24 Sep 2016 20:46:26 -0700 [thread overview]
Message-ID: <1474775186.23838.23.camel@perches.com> (raw)
In-Reply-To: <201609251139.vxagmOPP%fengguang.wu@intel.com>
On Sun, 2016-09-25 at 11:40 +0800, kbuild test robot wrote:
> Hi Joe,
Hey Fengguang
> It's probably a bug fix that unveils the link errors.
I think all of these reports about compiler-gcc integrations
are bogons.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 9c0e28a7be656d737fb18998e2dcb0b8ce595643
> commit: cb984d101b30eb7478d32df56a0023e4603cba7f compiler-gcc: integrate the various compiler-gcc[345].h files
> date: 1 year, 3 months ago
> config: m32r-allnoconfig (attached as .config)
> compiler: m32r-linux-gcc (GCC) 6.2.0
> 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 cb984d101b30eb7478d32df56a0023e4603cba7f
> # save the attached .config to linux build tree
> make.cross ARCH=m32r
>
>
> All errors (new ones prefixed by >>):
>
>
> arch/m32r/kernel/built-in.o: In function `default_eit_handler':
> > > (.text+0x3fc): undefined reference to `printk'
There isn't any association to integration here.
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: undefined reference to `printk'
Date: Sat, 24 Sep 2016 20:46:26 -0700 [thread overview]
Message-ID: <1474775186.23838.23.camel@perches.com> (raw)
In-Reply-To: <201609251139.vxagmOPP%fengguang.wu@intel.com>
On Sun, 2016-09-25 at 11:40 +0800, kbuild test robot wrote:
> Hi Joe,
Hey Fengguang
> It's probably a bug fix that unveils the link errors.
I think all of these reports about compiler-gcc integrations
are bogons.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 9c0e28a7be656d737fb18998e2dcb0b8ce595643
> commit: cb984d101b30eb7478d32df56a0023e4603cba7f compiler-gcc: integrate the various compiler-gcc[345].h files
> date: 1 year, 3 months ago
> config: m32r-allnoconfig (attached as .config)
> compiler: m32r-linux-gcc (GCC) 6.2.0
> 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 cb984d101b30eb7478d32df56a0023e4603cba7f
> # save the attached .config to linux build tree
> make.cross ARCH=m32r
>
>
> All errors (new ones prefixed by >>):
>
>
> arch/m32r/kernel/built-in.o: In function `default_eit_handler':
> > > (.text+0x3fc): undefined reference to `printk'
There isn't any association to integration here.
>
next prev parent reply other threads:[~2016-09-25 3:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 3:40 undefined reference to `printk' kbuild test robot
2016-09-25 3:46 ` Joe Perches [this message]
2016-09-25 3:46 ` Joe Perches
2016-09-26 1:54 ` Fengguang Wu
2016-09-26 1:54 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2016-09-10 17:10 kbuild test robot
2016-09-05 8:04 kbuild test robot
2016-08-28 16:56 kbuild test robot
2016-08-16 1:20 kbuild test robot
2016-08-07 7:17 kbuild test robot
2016-07-27 20:56 kbuild test robot
2016-07-27 20:56 ` kbuild test robot
2016-07-19 9:10 kbuild test robot
2016-07-19 9:10 ` kbuild test robot
2016-07-03 15:39 kbuild test robot
2016-07-03 15:39 ` kbuild test robot
2016-06-26 1:19 kbuild test robot
2016-06-26 1:19 ` kbuild test robot
2016-06-27 5:14 ` Yoshinori Sato
2016-06-27 5:14 ` Yoshinori Sato
2016-06-12 2:17 kbuild test robot
2016-06-12 2:17 ` kbuild test robot
2016-06-12 4:38 ` Josh Triplett
2016-06-12 4:38 ` Josh Triplett
2016-06-12 4:38 ` Josh Triplett
2016-06-12 4:38 ` Josh Triplett
2016-06-27 5:26 ` Yoshinori Sato
2016-06-27 5:26 ` Yoshinori Sato
2016-06-05 0:43 kbuild test robot
2016-06-05 0:43 ` kbuild test robot
2002-04-23 13:34 undefined reference to printk() gio zanei
2002-04-23 13:56 ` Richard B. Johnson
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=1474775186.23838.23.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.