From: Ananth N Mavinakayanahalli <ananth@in•ibm.com>
To: Alexander Beregalov <a.beregalov@gmail•com>
Cc: linux-next@vger•kernel.org, sparclinux <sparclinux@vger•kernel.org>
Subject: Re: build failure on sparc64 (Re: linux-next: Tree for October 27)
Date: Tue, 28 Oct 2008 10:05:23 +0530 [thread overview]
Message-ID: <20081028043523.GA3113@in.ibm.com> (raw)
In-Reply-To: <a4423d670810270843j55cf1bd9s223aaa447667903e@mail.gmail.com>
On Mon, Oct 27, 2008 at 07:43:24PM +0400, Alexander Beregalov wrote:
> 2008/10/27 Alexander Beregalov <a.beregalov@gmail•com>:
> > init/built-in.o: In function `start_kernel':
> > /home/alexb/linux-2.6/init/main.c:648: undefined reference to `locking_selftest'
> > kernel/built-in.o: In function `init_kprobes':
> > /home/alexb/linux-2.6/kernel/kprobes.c:1106: undefined reference to
> > `init_test_probes'
> >
>
> Hm, it was strange situation
>
> `make image` runs oldconfig, after that config was the following:
> CONFIG_KERNEL_TESTS disabled
> CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
> CONFIG_KPROBES_SANITY_TEST=y
>
> But they both are under "if KERNEL_TESTS" condition in test/Kconfig.
> Strange, I can not reproduce it anymore
No wonder :-) Stephen dropped the tests/ tree pending a decision on its
future.
You should however be able to select and run the tests from under the
'Kernel hacking' menu.
Ananth
next prev parent reply other threads:[~2008-10-28 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 15:16 build failure on sparc64 (Re: linux-next: Tree for October 27) Alexander Beregalov
2008-10-27 15:43 ` Alexander Beregalov
2008-10-28 4:35 ` Ananth N Mavinakayanahalli [this message]
2008-10-28 6:15 ` Stephen Rothwell
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=20081028043523.GA3113@in.ibm.com \
--to=ananth@in$(echo .)ibm.com \
--cc=a.beregalov@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sparclinux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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