From: Keith Owens <kaos@ocs.com.au>
To: Paul Mundt <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, sam@ravnborg.org,
pmarques@grupopie.com
Subject: Re: sh: inconsistent kallsyms data
Date: Sat, 01 Jan 2005 15:15:35 +1100 [thread overview]
Message-ID: <8025.1104552935@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 01 Jan 2005 14:59:19 +1100." <7184.1104551959@ocs3.ocs.com.au>
On Sat, 01 Jan 2005 14:59:19 +1100,
Keith Owens <kaos@ocs.com.au> wrote:
>Paul, please test this patch. Build with CONFIG_KALLSYMS_ALL=n and
>CONFIG_KALLSYMS_EXTRA_PASS=n.
ps. Due to bugs in the kernel build system, you cannot assume that
changing scripts/kallsyms.c or CONFIG_KALLSYMS_ALL or
CONFIG_KALLSYMS_EXTRA_PASS will be automatically detected. The make
dependency tree for the kallsyms code is incomplete.
After applying the patch and adjusting the config, touch init/main.c
then make. Touching a file will force a kernel relink and work around
the incomplete dependency data.
next prev parent reply other threads:[~2005-01-01 4:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 17:25 sh: inconsistent kallsyms data Paul Mundt
2004-12-31 17:59 ` pmarques
2004-12-31 18:22 ` Paul Mundt
2004-12-31 19:29 ` pmarques
2004-12-31 19:42 ` Paul Mundt
2004-12-31 18:15 ` Keith Owens
2005-01-01 3:59 ` Keith Owens
2005-01-01 4:15 ` Keith Owens [this message]
2005-01-01 9:01 ` Paul Mundt
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=8025.1104552935@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=sam@ravnborg.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