Bug 64648 – Kernel 2.4.xxx dosn't compile conflict with FASTCALL

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Bernd Martin Wollny 2004-09-19 08:39:49 UTC]

I can not compile the 2.4.2x kernel.I tried vanilla and gentoo kernel.



Reproducible: Always
Steps to Reproduce:

Actual Results:  
 scripts/mkversion > .tmpversion
gcc -D__KERNEL__ -I/usr/src/linux-2.4.27/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe
-mpreferred-stack-boundary=2 -march=i686  -DUTS_MACHINE='"i386"'
-DKBUILD_BASENAME=version -c -o init/version.oinit/version.c
make CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.27/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 " -C  kernel
make[1]: Entering directory `/usr/src/linux-2.4.27/kernel'
make all_targets
make[2]: Entering directory `/usr/src/linux-2.4.27/kernel'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.27/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe
-mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include
-DKBUILD_BASENAME=sched  -fno-omit-frame-pointer -c -o sched.o sched.c
sched.c:409: error: conflicting types for 'schedule_timeout'
/usr/src/linux-2.4.27/include/linux/sched.h:148: error: previous declaration of
'schedule_timeout' was here
sched.c:409: error: conflicting types for 'schedule_timeout'
/usr/src/linux-2.4.27/include/linux/sched.h:148: error: previous declaration of
'schedule_timeout' was here
sched.c:739: error: conflicting types for '__wake_up'
/usr/src/linux-2.4.27/include/linux/sched.h:595: error: previous declaration of
'__wake_up' was here
sched.c:739: error: conflicting types for '__wake_up'
/usr/src/linux-2.4.27/include/linux/sched.h:595: error: previous declaration of
'__wake_up' was here
sched.c:749: error: conflicting types for '__wake_up_sync'
/usr/src/linux-2.4.27/include/linux/sched.h:596: error: previous declaration of
'__wake_up_sync' was here
sched.c:749: error: conflicting types for '__wake_up_sync'
/usr/src/linux-2.4.27/include/linux/sched.h:596: error: previous declaration of
'__wake_up_sync' was here
sched.c:759: error: conflicting types for 'complete'
/usr/src/linux-2.4.27/include/linux/completion.h:31: error: previous declaration
of 'complete' was here
sched.c:759: error: conflicting types for 'complete'
/usr/src/linux-2.4.27/include/linux/completion.h:31: error: previous declaration
of 'complete' was here
sched.c:769: error: conflicting types for 'wait_for_completion'
/usr/src/linux-2.4.27/include/linux/completion.h:30: error: previous declaration
of 'wait_for_completion' was here
sched.c:769: error: conflicting types for 'wait_for_completion'
/usr/src/linux-2.4.27/include/linux/completion.h:30: error: previous declaration
of 'wait_for_completion' was here
sched.c:804: error: conflicting types for 'interruptible_sleep_on'
/usr/src/linux-2.4.27/include/linux/sched.h:600: error: previous declaration of
'interruptible_sleep_on' was here
sched.c:804: error: conflicting types for 'interruptible_sleep_on'
/usr/src/linux-2.4.27/include/linux/sched.h:600: error: previous declaration of
'interruptible_sleep_on' was here            

Expected Results:  
compile the Kernel

GCC 3.4.1
glibc 2.3.4-20040808

[Comment 1 Daniel Drake (RETIRED) 2004-09-26 06:58:21 UTC]

Can you please post your .config (as an attachment)

[Comment 2 Bernd Martin Wollny 2004-09-28 02:41:03 UTC]

Hello, 
i can Post you my config. But it's not depend on the .config I have tried it with my config. After this i tried it with:
make distclean ; make menuconfig - with no changes - only save the settings. 

I got always the same error. 

[Comment 3 Daniel Drake (RETIRED) 2004-09-28 05:44:11 UTC]

How about the output of "emerge info"?

[Comment 4 Luca Barbato 2004-10-01 16:12:12 UTC]

*** Bug 65177 has been marked as a duplicate of this bug. ***

[Comment 5 Luca Barbato 2004-10-01 16:16:40 UTC]

gcc-3.4.x just thinks that FASTCALL(foo()) != foo()

bumping the severity to critical since gcc-3.4.x is our default compiler

[Comment 6 Disenchanted (RETIRED) 2004-10-01 23:08:14 UTC]

gcc3.4 is not the default on x86

this should really be closed as upstream
2.4.28_pre3 might be worth a shot, it shows gcc3.4 fixes

  o gcc-3.4 fixes 1/3: fastcall mismatches
  o gcc-3.4 fixes 2/3: bogus lvalues
  o gcc-3.4 fixes 3/3: misc remaining issues

from:

http://www.kernel.org/pub/linux/kernel/v2.4/testing/patch-2.4.28.log

[Comment 7 Bernd Martin Wollny 2004-10-11 03:54:56 UTC]

Thank you for your help. In the meantime I have compiled the kernel with gcc-3.3.4.

bye and Thanks