From: Bill Davidsen <davidsen@tmr.com>
To: "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: can't compile kernels lately (2.6.16.5 and up)
Date: Thu, 27 Apr 2006 16:36:57 -0400 [thread overview]
Message-ID: <44512B69.2030504@tmr.com> (raw)
In-Reply-To: <2f4958ff0604260639n4874c2aua1e99ec4c32d2182@mail.gmail.com>
Grzegorz Jaśkiewicz wrote:
> root@puppet:/usr/src/linux-2.6.16.11# make
> CHK include/linux/version.h
> HOSTCC scripts/mod/file2alias.o
> scripts/mod/file2alias.c:386: warning: 'struct input_device_id'
> declared inside parameter list
> scripts/mod/file2alias.c:386: warning: its scope is only this
> definition or declaration, which is probably not what you want
Did you try
- save .config
- make distclean (or mrproper)
- restore .config
- make oldconfig
I think there's a corner case which patch application leaves file mod
dates wrong somehow.just "make clean" is a cure, but this is the big gun.
I realize you probably know this and tried it before asking, but it sure
looks like what I see which I brain fart and don't clean properly before
the next build,.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2006-04-27 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 13:39 Grzegorz Jaśkiewicz
2006-04-26 15:02 ` Gene Heskett
2006-04-26 15:17 ` Grzegorz Jaśkiewicz
[not found] ` <df47b87a0604260906m519cc6f5ud4d8527d4e5a243e@mail.gmail.com>
2006-04-26 16:22 ` Grzegorz Jaśkiewicz
[not found] ` <20060426093346.c36be5ff.rdunlap@xenotime.net>
[not found] ` <2f4958ff0604260938u759fdb53x950ca3cef34424e5@mail.gmail.com>
[not found] ` <20060426103801.b05bec5d.rdunlap@xenotime.net>
2006-04-26 18:06 ` Grzegorz Jaśkiewicz
2006-04-27 0:25 ` Gene Heskett
2006-04-27 20:36 ` Bill Davidsen [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=44512B69.2030504@tmr.com \
--to=davidsen@tmr.com \
--cc=gryzman@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome