From: Mark Pilon <mark.pilon@minolta-qms.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: gcc 3.0 for PPC
Date: Wed, 15 Aug 2001 13:26:15 -0600 [thread overview]
Message-ID: <3B7ACCD7.BCC0D2AA@minolta-qms.com> (raw)
if anyone is / has built gcc 3.0 for PPC I'd appreciate a word as
to how you configured it.
I built it configured:
./configure --host=i386-pc-linux-gnu --target=powerpc-linux
--prefix=/home/mpilon/ppc_tools --with-newlib -enable-languages=c
and got many warnings, mostly comparison between signed and unsigned ...
and it finally dies compiling ./libgcc2.c -o libgcc/./_muldi3.o
w/:
In file included from tm.h:6,
from config/rs6000/xm-sysv4.h:35,
from tconfig.h:3,
from libgcc2.c:36:
config/rs6000/linux.h:81:20: signal.h: No such file or directory
config/rs6000/linux.h:82:26: sys/ucontext.h: No such file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/home/mpilon/ppc_tools/gcc-3.0/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory `/home/mpilon/ppc_tools/gcc-3.0/gcc'
make: *** [all-gcc] Error 2
thanks,
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-15 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 19:26 Mark Pilon [this message]
2001-08-15 20:06 ` gcc 3.0 for PPC Amit D Chaudhary
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=3B7ACCD7.BCC0D2AA@minolta-qms.com \
--to=mark.pilon@minolta-qms.com \
--cc=linuxppc-embedded@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).