compile problem with current bk tree

compile problem with current bk tree

[Geert Uytterhoeven]

| make[2]: Entering directory `/extra/tmp/linuxppc_2_3/kernel'
| gcc -D__KERNEL__ -I/extra/tmp/linuxppc_2_3/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -DEXPORT_SYMTAB -c signal.c
| signal.c: In function `do_sigaction':
| signal.c:915: fixed or forbidden register 68 (0) was spilled for class CR0_REGS.This may be due to a compiler bug or to impossible asm statements or clauses.
| cpp: output pipe has been closed

| ccallisto$ gcc -v
| Reading specs from /usr/lib/gcc-lib/powerpc-linux/egcs-2.91.66/specs
| gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release)
| callisto$

Any suggestions?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: compile problem with current bk tree

[Andreas Tobler]

Geert Uytterhoeven wrote:
>
> | make[2]: Entering directory `/extra/tmp/linuxppc_2_3/kernel'
> | gcc -D__KERNEL__ -I/extra/tmp/linuxppc_2_3/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -DEXPORT_SYMTAB -c signal.c
> | signal.c: In function `do_sigaction':
> | signal.c:915: fixed or forbidden register 68 (0) was spilled for class CR0_REGS.This may be due to a compiler bug or to impossible asm statements or clauses.
> | cpp: output pipe has been closed
>
> | ccallisto$ gcc -v
> | Reading specs from /usr/lib/gcc-lib/powerpc-linux/egcs-2.91.66/specs
> | gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release)
> | callisto$
>
> Any suggestions?
Don't see it here, though I'm not sure if I'm up to date with bk-devel.
I rsynced it a few minutes ago. I gave up direct bk access since it eats
my hd, for each branch I need 300MB at least!!
The only difference I see, I use a gcc-2.95.2 19991024 from Franz.

Andreas

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: compile problem with current bk tree

[Franz Sirl]

At 08:37 12.05.00, Geert Uytterhoeven wrote:
>| ccallisto$ gcc -v
>| Reading specs from /usr/lib/gcc-lib/powerpc-linux/egcs-2.91.66/specs
>| gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release)
>| callisto$
>
>Any suggestions?

Use gcc-2.95.2 or later :-). egcs-1.1.2 is not recommended anymore for PPC.

Franz.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/