laptopkernel-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Laptopkernel-devel] non-compile problem with gcc 3.3


From: Sebastian Henschel
Subject: Re: [Laptopkernel-devel] non-compile problem with gcc 3.3
Date: Tue, 3 Jun 2003 15:37:40 +0200
User-agent: Mutt/1.5.4i

hello list..

Received at 2003-05-31 / 15:36 by Anders Karlsson:
> 
> On Fri, 2003-05-30 at 13:02, Jochen Michel wrote:
> > 
> > make[2]: Entering directory `/usr/src/linux-2.4.21-rc4/kernel'
> > gcc -D__KERNEL__ -I/usr/src/linux-2.4.21-rc4/include -Wall
> > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=pentium4
> >   -nostdinc -iwithprefix include -DKBUILD_BASENAME=sched
> > -fno-omit-frame-pointer -c -o sched.o sched.c
> > sched.c: In function `schedule':
> > sched.c:709: internal compiler error: in merge_assigned_reloads, at
> > reload1.c:6134
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> > make[2]: *** [sched.o] Error 1
> > make[2]: Leaving directory `/usr/src/linux-2.4.21-rc4/kernel'
> > make[1]: *** [first_rule] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.21-rc4/kernel'
> > make: *** [_dir_kernel] Error 2
> > 
> > 
> > Apparently there is some code from laptopkernel patch which does'nt
> > comply to the strict gcc 3.3 rules. SwSusp? Acpi?
> 
> I thought there was someone that figured out that it was swsusp that
> modified the file that breaks gcc. 

it really seems like that. if i disable swsusp, it compiles fine (though
it was only vanilla rc6 + acpi + swsusp).

> You might want to report back to the
> gcc team that the compiler breaks on the code and you might also want to

they already know that... in a way... see my first post, the bug report
on gcc-bugzilla ist just the very essence of the error. :)

> let the swsusp team know that. Either team might have a work-around
> available for the compiler you are using.

i just asked on swsusp-devel and pointed them to this discussion.

> Either way, the right answer it to get things working with gcc 3.3 as
> that compiler is not going to go away, quite the opposite. :)
> 
> Anyone disagree?

well, i suppose gcc 3.3.1 should be released with a fix as soon as
possible. :)

cheers,
 sebastian
-- 
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

Attachment: pgpfzcD1dwdvj.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]