From: Kumar Gala <kumar.gala@freescale.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, <linux-kernel@vger.kernel.org>
Subject: Re: kernel buildsystem error/warning?
Date: Mon, 17 Oct 2005 08:58:09 -0500 [thread overview]
Message-ID: <0B3F35F7-9558-4314-A330-594A9E5A539D@freescale.com> (raw)
In-Reply-To: <12922.194.237.142.21.1127462553.squirrel@194.237.142.21>
Sam,
Did you ever get around to this. It appears to still be "broken".
- kumar
On Sep 23, 2005, at 3:02 AM, Sam Ravnborg wrote:
>>>
>>>
>> After some more debug it appears that define rule_vmlinux__ is what's
>> causing this and in my .config CONFIG_KALLSYMS is not defined.
>>
>> Not sure if that will help. If I enable CONFIG_KALLSYMS the "error"
>> goes away (which makes sense based on the rule_vmlinux__) define.
>>
>
> Good info - thanks.
> I will fix it in the weekend.
>
> Sam
>
prev parent reply other threads:[~2005-10-17 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 13:45 kernel buildsystem error/warning? Kumar Gala
2005-09-23 4:49 ` Randy.Dunlap
2005-09-23 5:44 ` Kumar Gala
2005-09-23 6:10 ` Kumar Gala
2005-09-23 8:02 ` Sam Ravnborg
2005-10-17 13:58 ` Kumar Gala [this message]
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=0B3F35F7-9558-4314-A330-594A9E5A539D@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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;
as well as URLs for NNTP newsgroup(s).