From: Scott Wood <scott@broadlink.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: GLIBC wont compile for MPC860
Date: Wed, 01 Sep 1999 13:27:55 -0700 [thread overview]
Message-ID: <37CD8C4B.43C595EE@broadlink.com> (raw)
In-Reply-To: 19990831003953.707A564E@elph.research.canon.com.au
Graham Stoney wrote:
>
> Scott Wood writes:
> > The MPC8xx have no floating point, so it should be compiled with -msoft-float,
> > (I think)... ./configure --without-fp will do it.
>
> Is this implied when gcc has been configured --with-cpu=860?
I don't think so... I put -msoft-float into the sysdeps/powerpc/Makefile and I see
it twice below, so I would imagine that if you use both flags then -msoft-float
will be used.
I am using YellowDog Linux now and instead of an 'internal compiler error',
I get:
make[1]: Entering directory `/usr/src/redhat/SOURCES/glibc-2.1.1/math'
gcc ../sysdeps/powerpc/s_isnan.c -c -Wall -Winline -Wstrict-prototypes -Wwrite-strings -mcpu=860 -msoft-float -fpic
-msoft-float -Wno-uninitialized -Wno-write-strings -I../include -I. -I.. -I../libio -I../sysdeps/powerpc/elf
-I../sysdeps/unix/sysv/linux/powerpc -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/powerpc -I../sysdeps/wordsize-32
-I../sysdeps/ieee754 -I../sysdeps/libm-ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -include
../include/libc-symbols.h -DPIC -D__NO_MATH_INLINES -D__LIBC_INTERNAL_MATH_INLINES -DNO_LONG_DOUBLE -D_Mlong_double_=double -o
s_isnan.os
../sysdeps/powerpc/s_isnan.c: In function `__isnan':
../sysdeps/powerpc/s_isnan.c:32: fixed or forbidden register 32 (0) was spilled for class FLOAT_REGS.
This may be due to a compiler bug or to impossible asm
statements or clauses.
make[1]: *** [s_isnan.os] Error 1
I haven't even got a PowerPC 750 native build to work yet (even
though I ran configure with the --disable-time and --disable-db2 options). Any
idea how I can exclude db2 (and other unnecessary things like locale and nis)
support so I can get a (c)lean build?
I have been able to run many static binaries compiled for the 750 with
--msoft-float on the MPC850 just fine, although snmpd and dhcpd segfault. The
glibc should work as well if it doesn't do hardware floating point, but it doesn't
seem to compile without it.
-Scott
>
> Thanks,
> Graham
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-09-01 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 1:12 GLIBC wont compile for MPC860 Brendan Simon
1999-08-30 18:26 ` Scott Wood
1999-08-31 0:39 ` Graham Stoney
1999-09-01 20:27 ` Scott Wood [this message]
1999-09-01 21:47 ` David Edelsohn
1999-09-02 12:27 ` Marcus Sundberg
1999-09-03 2:15 ` Graham Stoney
1999-09-03 2:40 ` Michael Meissner
1999-09-03 12:18 ` Marcus Sundberg
1999-09-03 15:48 ` Dan Malek
1999-09-03 15:53 ` Grant Erickson
1999-09-06 1:15 ` Graham Stoney
1999-09-06 5:57 ` Dan Malek
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=37CD8C4B.43C595EE@broadlink.com \
--to=scott@broadlink.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).