From: David Relson <relson@osagesoftware.com>
To: linux-kernel@vger.kernel.org
Subject: Problem with kernel 2.6.15's build target .tmp_vmlinux1
Date: Tue, 10 Jan 2006 19:35:34 -0500 [thread overview]
Message-ID: <20060110193534.09a6031c@osage.osagesoftware.com> (raw)
Greetings,
I've run into a problem building 2.6.15. Starting with my 2.6.14
.config file, I ran oldconfig to generate a .config for 2.6.15.
Running "make" results in:
LD .tmp_vmlinux1
kernel/built-in.o: In function `do_exit':
: undefined reference to `exit_io_context'
mm/built-in.o: In function `generic_write_checks':
: undefined reference to `bdev_read_only'
mm/built-in.o: In function `__generic_file_aio_write_nolock':
: undefined reference to `bdev_read_only'
mm/built-in.o: In function `__alloc_pages':
: undefined reference to `blk_congestion_wait'
mm/built-in.o: In function `__alloc_pages':
: undefined reference to `blk_congestion_wait'
Makefile indicates that KALLSYMS is involved in building this target,
so here are two combinations of KALLSYMS settings that result in the
same problem:
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS is not set
# CONFIG_KALLSYMS is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
Makefile mentions that the maintainers are working on problems with
kallsyms, which is why I'm reporting this problem.
If you need any more info (such as a copy of .config), let me know.
Regards,
David
P.S. As I'm not subscribed to this list, please CC me for all replies.
next reply other threads:[~2006-01-11 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 0:35 David Relson [this message]
2006-01-13 14:01 ` Problem with kernel 2.6.15's build target .tmp_vmlinux1 Adrian Bunk
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=20060110193534.09a6031c@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--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 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.