From: Fengguang Wu <fengguang.wu@intel.com>
To: Hirokazu Takata <takata@linux-m32r.org>
Cc: linux-m32r@ml.linux-m32r.org, kbuild-all@01.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [m32r] ERROR: "memory_start" [fs/udf/udf.ko] undefined!
Date: Sun, 9 Mar 2014 09:26:28 +0800 [thread overview]
Message-ID: <20140309012628.GA9095@localhost> (raw)
Hi Hirokazu,
We noticed long standing build errors for m32104ut_defconfig and the
below bisected "first bad commit" actually fixed something to make the
kernel build go on to disclose these hidden errors.
first "bad" commit: fc31c7716355a226b8ed4e16f4581e5c8fa53570 kbuild: include limits.h in sumversion.c for PATH_MAX
date: 7 years ago
config: make ARCH=m32r m32104ut_defconfig
All error/warnings:
>> ERROR: "memory_start" [fs/udf/udf.ko] undefined!
>> ERROR: "memory_end" [fs/udf/udf.ko] undefined!
>> ERROR: "memory_end" [drivers/scsi/sg.ko] undefined!
>> ERROR: "memory_start" [drivers/scsi/sg.ko] undefined!
ERROR: "memory_end" [drivers/media/video/c-qcam.ko] undefined!
ERROR: "memory_start" [drivers/media/video/c-qcam.ko] undefined!
ERROR: "memory_end" [drivers/media/video/bw-qcam.ko] undefined!
ERROR: "memory_start" [drivers/media/video/bw-qcam.ko] undefined!
>> ERROR: "memory_end" [drivers/i2c/i2c-dev.ko] undefined!
>> ERROR: "memory_start" [drivers/i2c/i2c-dev.ko] undefined!
ERROR: "ioport_map" [drivers/i2c/busses/i2c-elektor.ko] undefined!
ERROR: "ioport_unmap" [drivers/i2c/busses/i2c-elektor.ko] undefined!
ERROR: "iowrite8" [drivers/i2c/busses/i2c-elektor.ko] undefined!
ERROR: "ioread8" [drivers/i2c/busses/i2c-elektor.ko] undefined!
---
0-DAY kernel build testing backend Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
reply other threads:[~2014-03-09 1:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140309012628.GA9095@localhost \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=takata@linux-m32r.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