From: Andreas Tobler <toa@pop.agri.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: compile problem with current bk tree
Date: Fri, 12 May 2000 10:11:54 +0200 [thread overview]
Message-ID: <391BBCCA.46B3ED69@pop.agri.ch> (raw)
In-Reply-To: Pine.GSO.4.10.10005120835040.2055-100000@dandelion.sonytel.be
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/
next prev parent reply other threads:[~2000-05-12 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-12 6:37 compile problem with current bk tree Geert Uytterhoeven
2000-05-12 8:11 ` Andreas Tobler [this message]
[not found] <Pine.GSO.4.10.10005120835040.2055-100000@dandelion.sonytel .be>
2000-05-12 12:36 ` Franz Sirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=391BBCCA.46B3ED69@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=a.tobler@schweiz.ch \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.