public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: gcc-help@gcc.gnu.org
Subject: I need help building a powerpc-unknown-eabispe cross compiler
Date: Tue, 02 Jan 2007 20:17:00 -0000	[thread overview]
Message-ID: <20070102201740.GB3563@sygehus.dk> (raw)

   I want to build a cross compiler with powerpc-unknown-eabispe as target
and i686-pc-linux-gnu as host. If I configure it like this (all on one line)

 ../../src/gcc/configure --enable-sim --with-newlib --disable-nls
 --enable-e500_double --prefix=${HOME} --enable-checking=yes,rtl
 --disable-threads --disable-shared --without-long-double-128
 --target=powerpc-unknown-eabispe

in a combined tree with gcc, binutils, gdb and newlib, the build fails
compiling libgcc2:

/home/rask/build/gcc-ppc/./gcc/xgcc -B/home/rask/build/gcc-ppc/./gcc/ -nostdinc -B/home/rask/build/gcc-ppc/powerpc-unknown-eabispe/newlib/ -isystem /home/rask/build/gcc-ppc/powerpc-unknown-eabispe/newlib/targ-include -isystem /home/rask/src/gcc/newlib/libc/include -B/home/rask/powerpc-unknown-eabispe/bin/ -B/home/rask/powerpc-unknown-eabispe/lib/ -isystem /home/rask/powerpc-unknown-eabispe/include -isystem /home/rask/powerpc-unknown-eabispe/sys-include -L/home/rask/build/gcc-ppc/./ld -O2  -O2 -g -O2  -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include   -specs=ldblspecs -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../../src/gcc/gcc -I../../../src/gcc/gcc/. -I../../../src/gcc/gcc/../include -I../../../src/gcc/gcc/../libcpp/include  -I../../../src/gcc/gcc/../libdecnumber -I../libdecnumber -DL_powitf2 -c ../../../src/gcc/gcc/libgcc2.c -o libgcc/./_powitf2.o
../../../src/gcc/gcc/libgcc2.c: In function '__powitf2':
../../../src/gcc/gcc/libgcc2.c:1735: internal compiler error: in gen_reg_rtx, at emit-rtl.c:770

   What is a know good way of doing it?

   FWIW, I also tried with --target=powerpc-none-linux-gnuspe, which builds
libgcc2 fine, but then target libiberty fails because I don't have the
header files it needs.

-- 
Rask Ingemann Lambertsen

             reply	other threads:[~2007-01-02 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 20:17 Rask Ingemann Lambertsen [this message]
2007-01-02 21:17 ` Rask Ingemann Lambertsen
2007-01-06 16:33   ` Rask Ingemann Lambertsen

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=20070102201740.GB3563@sygehus.dk \
    --to=rask@sygehus.dk \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).