Problems building 2.6.26 and 2.6.27-rc1
I'm getting the following error when trying to build either 2.6.26 or 2.6.27-rc1:
arch/x86/kernel/head64.c: In function ‘x86_64_start_kernel’:arch/x86/kernel/head64.c:88: error: size of array ‘type name’ is negative
Systems I've tried are DL585 G5 with dual-core Opterons and ML370 G5 with dual-core Intel. Both were originally installed using an x86_64 distro.
Anybody else seen this? Any workarounds?
Thanks,
mikem
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines
I'm getting the following error when trying to build either 2.6.26 or 2.6.27-rc1:
arch/x86/kernel/head64.c: In function ‘x86_64_start_kernel’:arch/x86/kernel/head64.c:88: error: size of array ‘type name’ is negative
It looks like you're hitting
BUILD_BUG_ON(!(MODULES_VADDR > __START_KERNEL));
No idea why you're hitting that though. What's your .config and compiler?
- R.
Quoted 12 lines
-----Original Message-----
From: Roland Dreier [mailto:[email protected]]
Sent: Wednesday, July 30, 2008 2:06 PM
To: Miller, Mike (OS Dev)
Cc: LKML; LKML-scsi
Subject: Re: Problems building 2.6.26 and 2.6.27-rc1Quoted 1 line
I'm getting the following error when trying to build
either 2.6.26 or > 2.6.27-rc1:
Quoted 1 line
Quoted 7 lines
Quoted 2 lines
arch/x86/kernel/head64.c: In function 'x86_64_start_kernel':arch/x86/kernel/head64.c:88: error: size of array 'typename' is negative
It looks like you're hitting
BUILD_BUG_ON(!(MODULES_VADDR > __START_KERNEL));
Same here, no idea why I'm hitting this...
Quoted 3 lines
No idea why you're hitting that though. What's your .config and compiler?
Compiler is gcc 4.1.2 20070626 (Red Hat 4.1.2-14).
Config file is attached.
-- mikem
Hmm, doesn't reproduce here with your config and gcc 4.1.
No idea, sorry.
- R.
Quoted 4 lines · Roland
Hmm, doesn't reproduce here with your config and gcc 4.1.
No idea, sorry.
Thanks for taking a look. This is perplexing. I know I've built this kernel, but sometimes I hit the build bug and sometimes I don't. I can't pinpoint any differences between working and non-working builds.
Anybody else? :)
-- mikem
Quoted 6 lines · Roland
Quoted 2 lines
I'm getting the following error when trying to build
either 2.6.26 or > 2.6.27-rc1:
Quoted 3 lines
arch/x86/kernel/head64.c: In function 'x86_64_start_kernel':arch/x86/kernel/head64.c:88: error: size of array 'type
Quoted 9 lines
name' is negative
It looks like you're hitting
BUILD_BUG_ON(!(MODULES_VADDR > __START_KERNEL));No idea why you're hitting that though. What's your .config and compiler?
I think maybe I've figured out what's breaking my build. If use "make -jN" I hit the error. I usually set N to the number of processors (real and HT). So if /proc/cpuinfo display info about 4 processors I use -j4, etc. If I don't specify the number of jobs to run simultaneously the build completes with just the usual warnings.
Any experts on parallelism out there?
-- mikem
Quoted 12 lines · Mike (OS Dev)
Quoted 10 lines · Roland
Quoted 2 lines
I'm getting the following error when trying to build
either 2.6.26 or > 2.6.27-rc1:
Quoted 3 lines
arch/x86/kernel/head64.c: In function 'x86_64_start_kernel':arch/x86/kernel/head64.c:88: error: size of array 'typename' is negative
It looks like you're hitting
Quoted 8 lines
Quoted 5 lines
BUILD_BUG_ON(!(MODULES_VADDR > __START_KERNEL));No idea why you're hitting that though. What's your .config and compiler?
I think maybe I've figured out what's breaking my build. If use "make -jN" I hit the error. I usually set N to the number of processors (real and HT). So if
/proc/cpuinfodisplay info about 4 processors I use -j4, etc. If I don't specify the number of jobs to run simultaneously the build completes with just the usual warnings.Any experts on parallelism out there?
Can you post the output of a make -j4 V=1 run that fials and one that succeeds. Then we can maybe spot something.
Sam
Quoted 27 lines · Sam
Quoted 8 lines · Mike (OS Dev)
Quoted 6 lines · Roland
Quoted 2 lines
I'm getting the following error when trying to build either
2.6.26 or > 2.6.27-rc1:
Quoted 3 lines
arch/x86/kernel/head64.c: In function 'x86_64_start_kernel':arch/x86/kernel/head64.c:88: error: size of array'type name' is
Quoted 10 lines
Quoted 9 lines
negative
It looks like you're hitting
BUILD_BUG_ON(!(MODULES_VADDR > __START_KERNEL));No idea why you're hitting that though. What's your .config and compiler?
I think maybe I've figured out what's breaking my build. If
use "make -jN" I hit the error. I usually set N to the number of processors (real and HT). So if
/proc/cpuinfodisplay info about 4 processors I use -j4, etc. If I don't specify the number of jobs to run simultaneously the build completes with just the usual warnings.Quoted 1 line
Quoted 7 lines
Quoted 1 line
Any experts on parallelism out there?
Can you post the output of a make -j4 V=1 run that fials and one that succeeds.
Then we can maybe spot something.Sam
Sure. Not to be stupid, but do you want the entire output from the builds or just what would go to stderr?
-- mikem
Quoted 29 lines · Mike (OS Dev)
Quoted 27 lines · Sam
Quoted 8 lines · Mike (OS Dev)
Quoted 6 lines · Roland
Quoted 2 lines
I'm getting the following error when trying to build either
2.6.26 or > 2.6.27-rc1:
Quoted 3 lines
arch/x86/kernel/head64.c: In function 'x86_64_start_kernel':arch/x86/kernel/head64.c:88: error: size of array'type name' is
Quoted 10 lines
Quoted 9 lines
negative
It looks like you're hitting
BUILD_BUG_ON(!(MODULES_VADDR > __START_KERNEL));No idea why you're hitting that though. What's your .config and compiler?
I think maybe I've figured out what's breaking my build. If
use "make -jN" I hit the error. I usually set N to the number of processors (real and HT). So if
/proc/cpuinfodisplay info about 4 processors I use -j4, etc. If I don't specify the number of jobs to run simultaneously the build completes with just the usual warnings.Quoted 1 line
Quoted 8 lines
Quoted 7 lines
Quoted 1 line
Any experts on parallelism out there?
Can you post the output of a make -j4 V=1 run that fials and one that succeeds.
Then we can maybe spot something.Sam
Sure. Not to be stupid, but do you want the entire output from the builds or just what would go to stderr?
Entire output please.
Sam