[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46000121.7070509@oracle.com>
Date: Tue, 20 Mar 2007 08:43:29 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Sam Ravnborg <sam@...nborg.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: 2.6.21-rc3-mm2
Sam Ravnborg wrote:
> On Mon, Mar 19, 2007 at 05:27:11PM -0700, Randy Dunlap wrote:
>> On Wed, 7 Mar 2007 20:19:15 -0800 Andrew Morton wrote:
>>
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/
>>>
>>> - This is the same as 2.6.21-rc3-mm1, except Con's CPU scheduler changes
>>> were dropped.
>>>
>>> This is for A/B comparison purposes, and because those changes crashed on
>>> one test setup.
>> I don't quite see why this error is happening. Looks like all
>> the nested #includes should handle it...
>>
>> CONFIG_KEXEC=y
>> CONFIG_CRASH_DUMP=y
>> CONFIG_UTRACE=y
>> # PTRACE=n
>> # PROC_FS=n
>>
>> In file included from arch/x86_64/kernel/crash.c:19:
>> include/linux/elfcore.h: In function 'elf_core_copy_regs':
>> include/linux/elfcore.h:103: error: dereferencing pointer to incomplete type
>> include/linux/elfcore.h:103: error: dereferencing pointer to incomplete type
>> make[1]: *** [arch/x86_64/kernel/crash.o] Error 1
>> make: *** [arch/x86_64/kernel] Error 2
>
> make arch/x86_64/kernel/crash.i
> may tell you a bit more why the includes foes wrong.
That didn't complain or have any errors/warnings, so hopefully
Roland can see something.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists