2002-06-19 08:12:48

by Joseph Pingenot

[permalink] [raw]
Subject: Build problem in sched.c in 2.5.23

make[1]: Entering directory `/usr/local/src/kernel/linux-2.5.23/kernel'
gcc -Wp,-MD,./.sched.o.d -D__KERNEL__ -I/usr/local/src/kernel/linux-2.5.23/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -fno-omit-frame-pointer -DKBUILD_BASENAME=sched -c -o sched.o sched.c
sched.c: In function `sys_sched_setaffinity':
sched.c:1332: `cpu_online_map' undeclared (first use in this function)
sched.c:1332: (Each undeclared identifier is reported only once
sched.c:1332: for each function it appears in.)
sched.c: In function `sys_sched_getaffinity':
sched.c:1391: `cpu_online_map' undeclared (first use in this function)
make[1]: *** [sched.o] Error 1
make[1]: Leaving directory `/usr/local/src/kernel/linux-2.5.23/kernel'
make: *** [kernel] Error 2

Need any more details?
--
Joseph======================================================jap3003@ksu.edu
"[...]this, they say, cost about $40 too much, and about 20,000 Iowans
bought [Windows] 98. Which gives us a tab of $800,000, i.e. the
equivalent of a rounding error in Redmond's vast war chest." -The Register


2002-06-19 08:22:21

by Erlend Aasland

[permalink] [raw]
Subject: Re: Build problem in sched.c in 2.5.23

On Wed, Jun 19, 2002 at 03:12:48AM -0500, Joseph Pingenot wrote:
> sched.c:1391: `cpu_online_map' undeclared (first use in this function)
>
> Need any more details?

Linus posted a patch for this:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102446529018948&w=2

2002-06-19 08:22:46

by Adrian Bunk

[permalink] [raw]
Subject: Re: Build problem in sched.c in 2.5.23

On Wed, 19 Jun 2002, Joseph Pingenot wrote:

> make[1]: Entering directory `/usr/local/src/kernel/linux-2.5.23/kernel'
> gcc -Wp,-MD,./.sched.o.d -D__KERNEL__ -I/usr/local/src/kernel/linux-2.5.23/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -fno-omit-frame-pointer -DKBUILD_BASENAME=sched -c -o sched.o sched.c
> sched.c: In function `sys_sched_setaffinity':
> sched.c:1332: `cpu_online_map' undeclared (first use in this function)
> sched.c:1332: (Each undeclared identifier is reported only once
> sched.c:1332: for each function it appears in.)
> sched.c: In function `sys_sched_getaffinity':
> sched.c:1391: `cpu_online_map' undeclared (first use in this function)
> make[1]: *** [sched.o] Error 1
> make[1]: Leaving directory `/usr/local/src/kernel/linux-2.5.23/kernel'
> make: *** [kernel] Error 2
>
> Need any more details?


The following patch that is already in Linus' BK repository fixes it:


--- a/include/linux/smp.h Wed Jun 19 00:00:41 2002
+++ b/include/linux/smp.h Wed Jun 19 00:00:41 2002
@@ -86,6 +86,7 @@
#define smp_call_function(func,info,retry,wait) ({ 0; })
static inline void smp_send_reschedule(int cpu) { }
static inline void smp_send_reschedule_all(void) { }
+#define cpu_online_map 1
#define cpu_online(cpu) 1
#define num_online_cpus() 1
#define __per_cpu_data

cu
Adrian

--

You only think this is a free country. Like the US the UK spends a lot of
time explaining its a free country because its a police state.
Alan Cox

2002-06-19 14:46:01

by Oliver Pitzeier

[permalink] [raw]
Subject: New Build problem in sched.c in 2.5.23 on an Alpha

I got another problem in sched.c

In file included from sched.c:26:
make[1]: Entering directory `/usr/src/linux-2.5.23/kernel'
gcc -Wp,-MD,./.sched.o.d -D__KERNEL__ -I/usr/src/linux-2.5.23/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5
-Wa,-mev6 -nostdinc -iwithprefix include -fno-omit-frame-pointer
-DKBUILD_BASENAME=sched -c -o sched.o sched.c
In file included from sched.c:26:
/usr/src/linux-2.5.23/include/asm/mmu_context.h: In function
`init_new_context':
/usr/src/linux-2.5.23/include/asm/mmu_context.h:230: `smp_num_cpus'
undeclared (first use in this function)
/usr/src/linux-2.5.23/include/asm/mmu_context.h:230: (Each undeclared
identifier is reported only once
/usr/src/linux-2.5.23/include/asm/mmu_context.h:230: for each function
it appears in.)
/usr/src/linux-2.5.23/include/asm/mmu_context.h:231: warning: implicit
declaration of function `cpu_logical_map'
sched.c: In function `try_to_wake_up':
sched.c:362: warning: label `repeat_lock_task' defined but not used
sched.c: In function `schedule':
sched.c:822: warning: implicit declaration of function
`prepare_arch_schedule'
sched.c:879: warning: implicit declaration of function
`prepare_arch_switch'
sched.c:883: warning: implicit declaration of function
`finish_arch_switch'
sched.c:886: warning: implicit declaration of function
`finish_arch_schedule'
make[1]: *** [sched.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.5.23/kernel'
make: *** [kernel] Error 2

Any ideas?

Greetz,
Oliver


2002-06-19 14:53:31

by Holzrichter, Bruce

[permalink] [raw]
Subject: RE: New Build problem in sched.c in 2.5.23 on an Alpha


> sched.c: In function `schedule':
> sched.c:822: warning: implicit declaration of function
> `prepare_arch_schedule'
> sched.c:879: warning: implicit declaration of function
> `prepare_arch_switch'
> sched.c:883: warning: implicit declaration of function
> `finish_arch_switch'
> sched.c:886: warning: implicit declaration of function
> `finish_arch_schedule'
> make[1]: *** [sched.o] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.5.23/kernel'
> make: *** [kernel] Error 2

What Arch are you on? Alpha?

Search the archive, you'll see that some of these are from Ingo's scheduler
changes.

B.

2002-06-19 15:42:42

by Oliver Pitzeier

[permalink] [raw]
Subject: RE: New Build problem in sched.c in 2.5.23 on an Alpha

Bruce Holzrichter wrote:
[ ... ]
> What Arch are you on? Alpha?

Yes, it's an Alpha.

> Search the archive, you'll see that some of these are from
> Ingo's scheduler changes.

I found some information which helped me. This problem is now
solved, but I got a new _strange_ one... I'm not a a asm-gure, so
I don't know how to handle _this_................ Are all these
errors because of the missing "regdef.h"? And if yes, why is it
missing!? :-(

Here it comes:
[ ... ]
gcc -Wp,-MD,./.stxcpy.o.d -D__ASSEMBLY__ -D__KERNEL__
-I/usr/src/linux-2.5.23/include -nostdinc -iwithprefix includ
e -D__KERNEL__ -I/usr/src/linux-2.5.23/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fn
o-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5
-Wa,-mev6 -c -o stxcpy.o stxcpy.S
stxcpy.S:23:26: alpha/regdef.h: No such file or directory
stxcpy.S: Assembler messages:
stxcpy.S:46: Error: inappropriate arguments for opcode `lda'
stxcpy.S:47: Error: inappropriate arguments for opcode `mskqh'
stxcpy.S:48: Error: inappropriate arguments for opcode `mskqh'
stxcpy.S:49: Error: inappropriate arguments for opcode `ornot'
stxcpy.S:50: Error: inappropriate arguments for opcode `mskql'
stxcpy.S:51: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:52: Error: inappropriate arguments for opcode `or'
stxcpy.S:53: Error: inappropriate arguments for opcode `bne'
stxcpy.S:60: Error: syntax error
stxcpy.S:61: Error: inappropriate arguments for opcode `addq'
stxcpy.S:62: Error: syntax error
stxcpy.S:63: Error: inappropriate arguments for opcode `addq'
stxcpy.S:64: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:65: Error: inappropriate arguments for opcode `beq'
stxcpy.S:72: Error: inappropriate arguments for opcode `negq'
stxcpy.S:73: Error: inappropriate arguments for opcode `and'
stxcpy.S:77: Error: inappropriate arguments for opcode `and'
stxcpy.S:78: Error: inappropriate arguments for opcode `bne'
stxcpy.S:82: Error: syntax error
stxcpy.S:83: Error: inappropriate arguments for opcode `subq'
stxcpy.S:84: Error: inappropriate arguments for opcode `zapnot'
stxcpy.S:85: Error: inappropriate arguments for opcode `or'
stxcpy.S:86: Error: inappropriate arguments for opcode `zap'
stxcpy.S:87: Error: inappropriate arguments for opcode `or'
stxcpy.S:89: Error: syntax error
stxcpy.S:102: Error: inappropriate arguments for opcode `xor'
stxcpy.S:104: Error: inappropriate arguments for opcode `and'
stxcpy.S:105: Error: inappropriate arguments for opcode `bne'
stxcpy.S:108: Error: syntax error
stxcpy.S:109: Error: inappropriate arguments for opcode `and'
stxcpy.S:110: Error: inappropriate arguments for opcode `addq'
stxcpy.S:111: Error: inappropriate arguments for opcode `beq'
stxcpy.S:112: Error: syntax error
stxcpy.S:131: Error: syntax error
stxcpy.S:132: Error: inappropriate arguments for opcode `addq'
stxcpy.S:134: Error: inappropriate arguments for opcode `extql'
stxcpy.S:135: Error: inappropriate arguments for opcode `extqh'
stxcpy.S:136: Error: inappropriate arguments for opcode `mskql'
stxcpy.S:137: Error: inappropriate arguments for opcode `or'
stxcpy.S:138: Error: inappropriate arguments for opcode `mskqh'
stxcpy.S:139: Error: inappropriate arguments for opcode `or'
stxcpy.S:141: Error: inappropriate arguments for opcode `or'
stxcpy.S:142: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:143: Error: inappropriate arguments for opcode `lda'
stxcpy.S:144: Error: inappropriate arguments for opcode `bne'
stxcpy.S:146: Error: inappropriate arguments for opcode `mskql'
stxcpy.S:147: Error: inappropriate arguments for opcode `or'
stxcpy.S:148: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:149: Error: inappropriate arguments for opcode `bne'
stxcpy.S:154: Error: syntax error
stxcpy.S:155: Error: inappropriate arguments for opcode `addq'
stxcpy.S:156: Error: inappropriate arguments for opcode `extql'
stxcpy.S:157: Error: syntax error
stxcpy.S:158: Error: inappropriate arguments for opcode `addq'
stxcpy.S:159: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:161: Error: inappropriate arguments for opcode `bne'
stxcpy.S:178: Error: inappropriate arguments for opcode `extqh'
stxcpy.S:179: Error: inappropriate arguments for opcode `addq'
stxcpy.S:180: Error: inappropriate arguments for opcode `extql'
stxcpy.S:181: Error: inappropriate arguments for opcode `addq'
stxcpy.S:182: Error: inappropriate arguments for opcode `or'
stxcpy.S:183: Error: syntax error
stxcpy.S:184: Error: syntax error
stxcpy.S:185: Error: inappropriate arguments for opcode `mov'
stxcpy.S:186: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:187: Error: inappropriate arguments for opcode `beq'
stxcpy.S:198: Error: inappropriate arguments for opcode `extqh'
stxcpy.S:199: Error: inappropriate arguments for opcode `or'
stxcpy.S:201: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:202: Error: inappropriate arguments for opcode `bne'
stxcpy.S:205: Error: syntax error
stxcpy.S:206: Error: inappropriate arguments for opcode `addq'
stxcpy.S:207: Error: inappropriate arguments for opcode `extql'
stxcpy.S:208: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:215: Error: inappropriate arguments for opcode `negq'
stxcpy.S:216: Error: inappropriate arguments for opcode `and'
stxcpy.S:218: Error: inappropriate arguments for opcode `and'
stxcpy.S:219: Error: inappropriate arguments for opcode `bne'
stxcpy.S:221: Error: syntax error
stxcpy.S:222: Error: inappropriate arguments for opcode `subq'
stxcpy.S:223: Error: inappropriate arguments for opcode `or'
stxcpy.S:224: Error: inappropriate arguments for opcode `zapnot'
stxcpy.S:225: Error: inappropriate arguments for opcode `zap'
stxcpy.S:226: Error: inappropriate arguments for opcode `or'
stxcpy.S:228: Error: syntax error
stxcpy.S:235: Error: syntax error
stxcpy.S:237: Error: inappropriate arguments for opcode `and'
stxcpy.S:238: Error: inappropriate arguments for opcode `and'
stxcpy.S:243: Error: inappropriate arguments for opcode `mov'
stxcpy.S:244: Error: inappropriate arguments for opcode `mov'
stxcpy.S:245: Error: inappropriate arguments for opcode `beq'
stxcpy.S:246: Error: syntax error
stxcpy.S:247: Error: inappropriate arguments for opcode `lda'
stxcpy.S:248: Error: inappropriate arguments for opcode `mskql'
stxcpy.S:250: Error: inappropriate arguments for opcode `subq'
stxcpy.S:255: Error: inappropriate arguments for opcode `cmplt'
stxcpy.S:256: Error: inappropriate arguments for opcode `beq'
stxcpy.S:258: Error: inappropriate arguments for opcode `lda'
stxcpy.S:259: Error: inappropriate arguments for opcode `mskqh'
stxcpy.S:261: Error: inappropriate arguments for opcode `ornot'
stxcpy.S:262: Error: inappropriate arguments for opcode `cmpbge'
stxcpy.S:263: Error: inappropriate arguments for opcode `beq'
stxcpy.S:270: Error: syntax error
stxcpy.S:272: Error: inappropriate arguments for opcode `negq'
stxcpy.S:273: Error: inappropriate arguments for opcode `and'
stxcpy.S:274: Error: inappropriate arguments for opcode `and'
stxcpy.S:275: Error: inappropriate arguments for opcode `subq'
stxcpy.S:276: Error: inappropriate arguments for opcode `or'
stxcpy.S:277: Error: inappropriate arguments for opcode `srl'
stxcpy.S:279: Error: inappropriate arguments for opcode `zapnot'
stxcpy.S:280: Error: inappropriate arguments for opcode `and'
stxcpy.S:281: Error: inappropriate arguments for opcode `extql'
stxcpy.S:282: Error: inappropriate arguments for opcode `extql'
stxcpy.S:284: Error: inappropriate arguments for opcode `andnot'
stxcpy.S:285: Error: inappropriate arguments for opcode `or'
stxcpy.S:286: Error: syntax error
make[1]: *** [stxcpy.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.5.23/arch/alpha/lib'
make: *** [arch/alpha/lib] Error 2

Ideas?

-Oliver