View previous topic :: View next topic |
Author |
Message |
Master One l33t
Joined: 25 Aug 2003 Posts: 754 Location: Austria
|
Posted: Wed Jun 09, 2004 6:11 pm Post subject: mm-sources 2.6.7-rc3-mm1 broken? |
|
|
I just tried to install the lastest mm-sources, but it looks like there is something broken, the compile stopped at drivers/perfctr/x86.c with a lot of errors (I am not at that workstation any more, so I can't post the error output). _________________ Las torturas mentales de la CIA |
|
Back to top |
|
|
Master One l33t
Joined: 25 Aug 2003 Posts: 754 Location: Austria
|
Posted: Fri Jun 11, 2004 8:04 am Post subject: |
|
|
Hm, either noone else is using mm-sources, or I am really the only one who experienced this problem.
Have a look at the error output:
Code: | linux # make
make[1]: >>arch/i386/kernel/asm-offsets.s<< ist bereits aktualisiert.
CHK include/linux/compile.h
CC drivers/perfctr/x86.o
distcc[16222] ERROR: compile /root/.ccache/x86.tmp.privatmaster.16218.i on localhost failed
drivers/perfctr/x86.c: In Funktion >>finalise_backpatching<<:
drivers/perfctr/x86.c:1137: error: Syntaxfehler before '{' token
drivers/perfctr/x86.c:1133: Warnung: unused variable `cache'
drivers/perfctr/x86.c:1134: Warnung: unused variable `state'
drivers/perfctr/x86.c: Auf h?chster Ebene:
drivers/perfctr/x86.c:1138: Warnung: type defaults to `int' in declaration of `clear_perfctr_cpus_forbidden_mask'
drivers/perfctr/x86.c:1138: Warnung: function declaration isn't a prototype
drivers/perfctr/x86.c:1138: error: conflicting types for `clear_perfctr_cpus_forbidden_mask'
drivers/perfctr/x86.c:1117: error: previous declaration of `clear_perfctr_cpus_forbidden_mask'
drivers/perfctr/x86.c:1138: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1140: Warnung: type defaults to `int' in declaration of `cache'
drivers/perfctr/x86.c:1140: Warnung: Initialisierung erzeugt Ganzzahl von Zeiger ohne Typkonvertierung
drivers/perfctr/x86.c:1140: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1141: error: Syntaxfehler before numeric constant
drivers/perfctr/x86.c:1142: error: Syntaxfehler before numeric constant
drivers/perfctr/x86.c:1147: error: Syntaxfehler before '&' token
drivers/perfctr/x86.c:1147: Warnung: type defaults to `int' in declaration of `perfctr_cpu_sample'
drivers/perfctr/x86.c:1147: Warnung: function declaration isn't a prototype
drivers/perfctr/x86.c:1147: error: conflicting types for `perfctr_cpu_sample'
drivers/perfctr/x86.c:1087: error: previous declaration of `perfctr_cpu_sample'
drivers/perfctr/x86.c:1147: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1148: error: Syntaxfehler before '&' token
drivers/perfctr/x86.c:1148: Warnung: type defaults to `int' in declaration of `perfctr_cpu_resume'
drivers/perfctr/x86.c:1148: Warnung: function declaration isn't a prototype
drivers/perfctr/x86.c:1148: error: conflicting types for `perfctr_cpu_resume'
drivers/perfctr/x86.c:1066: error: previous declaration of `perfctr_cpu_resume'
drivers/perfctr/x86.c:1148: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1149: error: Syntaxfehler before '&' token
drivers/perfctr/x86.c:1149: Warnung: type defaults to `int' in declaration of `perfctr_cpu_suspend'
drivers/perfctr/x86.c:1149: Warnung: function declaration isn't a prototype
drivers/perfctr/x86.c:1149: error: conflicting types for `perfctr_cpu_suspend'
drivers/perfctr/x86.c:1049: error: previous declaration of `perfctr_cpu_suspend'
drivers/perfctr/x86.c:1149: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1151: Warnung: type defaults to `int' in declaration of `set_perfctr_cpus_forbidden_mask'
drivers/perfctr/x86.c:1151: Warnung: Parameternamen (ohne Typen) in Funktionsdeklaration
drivers/perfctr/x86.c:1151: error: conflicting types for `set_perfctr_cpus_forbidden_mask'
drivers/perfctr/x86.c:1124: error: previous declaration of `set_perfctr_cpus_forbidden_mask'
drivers/perfctr/x86.c:1151: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1153: Warnung: type defaults to `int' in declaration of `redirect_call_disable'
drivers/perfctr/x86.c:1153: error: conflicting declarations of `redirect_call_disable'
drivers/perfctr/x86.c:908: error: `redirect_call_disable' previously declared here
drivers/perfctr/x86.c:1153: Warnung: data definition has no type or storage class
drivers/perfctr/x86.c:1154: error: Syntaxfehler before '}' token
{standard input}: Assembler messages:
{standard input}:1555: Error: symbol `redirect_call_disable' is already defined
{standard input}:1555: Warning: rest of line ignored; first ignored character is `,'
distcc[16218] ERROR: compile drivers/perfctr/x86.c on localhost failed
make[2]: *** [drivers/perfctr/x86.o] Fehler 1
make[1]: *** [drivers/perfctr] Fehler 2
make: *** [drivers] Fehler 2
linux # |
Also it tells distcc in the first ERROR line, it has nothing to do with it, I already tried it with distcc and ccache disabled.
The is my actual system-info:
Code: | linux # emerge info
Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.7-rc2-mm2)
=================================================================
System uname: 2.6.7-rc2-mm2 i686 AMD Athlon(tm) XP 3200+
Gentoo Base System version 1.4.16
distcc 2.14 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5
ACCEPT_KEYWORDS="x86 ~x86" |
glibc is compiled with NPTL support, but I already tried to recompile glibc with USE="-nptl" and afterwards gcc, but it leads to the same result. My actual sources 2.6.7-rc2-mm2 compile just fine, as well as the rest of my setup.
Anyone has any idea, what the problem could be?
Maybe something important changed in 2.6.7-rc3-mm1?
I used the same .config as for 2.6.7-rc2-mm2. _________________ Las torturas mentales de la CIA |
|
Back to top |
|
|
primero.gentoo Guru
Joined: 23 Dec 2003 Posts: 402
|
Posted: Fri Jun 11, 2004 8:11 am Post subject: |
|
|
EXcept for MSI i had no problem with compiling and using 2.6.7-rc3-love1 (based on rc3-mm1) so ... are you sure about your .config and your sources?
Bye _________________ "Linux, the choice of a GNU generation"
==Micro$oft - just say NO==
(L#USER 353039) |
|
Back to top |
|
|
Master One l33t
Joined: 25 Aug 2003 Posts: 754 Location: Austria
|
Posted: Fri Jun 11, 2004 8:15 am Post subject: |
|
|
Yes, my .config is OK; and I already unmerged and reemerged 2.6.7-rc3-mm1, just to be sure. Symlink is correkt as well of course.
I just checked the compile again without distcc and ccache, but it's indeed the same errors comming up.
I am also not using any fancy cflags:
Code: | CFLAGS="-march=athlon-xp -O3 -pipe -funroll-loops -fforce-addr -ftracer -fprefetch-loop-arrays -fomit-frame-pointer" |
At next I'll try the actual love sources. _________________ Las torturas mentales de la CIA |
|
Back to top |
|
|
Pink Veteran
Joined: 24 Jul 2003 Posts: 1062
|
Posted: Fri Jun 11, 2004 8:36 am Post subject: |
|
|
Don't worry, it's nothing serious, in the kernel options turn off the performance control option, just after the firmware options.
It is a new option in the mm-patch that is enabled by default. From what I can see, it causes compile problems for the majority of people and turning it off is the answer.
hth
[edit] You'll have to turn it off in the new love as well (love being patched on mm and all) |
|
Back to top |
|
|
Master One l33t
Joined: 25 Aug 2003 Posts: 754 Location: Austria
|
Posted: Fri Jun 11, 2004 10:49 am Post subject: |
|
|
Thanx for the hint, that was exactly the problem. Now both (2.6.7-rc3-mm1 & love-2.6.7-rc3-love1) compile just fine. _________________ Las torturas mentales de la CIA |
|
Back to top |
|
|
|