All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: gcc@gcc.gnu.org
Cc: parisc-linux@parisc-linux.org
Subject: [parisc-linux] Problem building gcc-3.2 (cvs head) on hppa-linux
Date: Fri, 12 Jul 2002 00:27:03 -0700	[thread overview]
Message-ID: <20020712072703.GA8838@tausq.org> (raw)

Trying to build CVS head (3.2 20020711) with:

configure --host=hppa-linux --build=hppa-linux --target=hppa64-linux
--enable-shared --disable-nls --enable-languages=c

I get:

/home/tausq/build/gcc-3.2/gcc/xgcc -B/home/tausq/build/gcc-3.2/gcc/ -B/home/tausq/opt/gnu/hppa64-linux/bin/ -B/home/tausq/opt/gnu/hppa64-linux/lib/ -isystem /home/tausq/opt/gnu/hppa64-linux/include -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fPIC -Dpa64=1 -DELF=1 -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
-I. -I/home/tausq/src/gcc-3.2/gcc -I/home/tausq/src/gcc-3.2/gcc/. -I/home/tausq/src/gcc-3.2/gcc/config -I/home/tausq/src/gcc-3.2/gcc/../include  -DL__gcc_bcmp -c /home/tausq/src/gcc-3.2/gcc/libgcc2.c -o libgcc/./__gcc_bcmp.o
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_frame_state_for':
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:906: warning: implicit declaration of function `memset'
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_install_context_1':
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1193: warning: implicit declaration of
function `memcpy'
In file included from /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1210:
/home/tausq/src/gcc-3.2/gcc/unwind.inc: In function `_Unwind_RaiseException':
/home/tausq/src/gcc-3.2/gcc/unwind.inc:132: error: Attempt to delete prologue/epilogue insn:
(insn 337 336 338 14 (nil) (set (reg:DI 7 %r7)
        (mem:DI (plus:DI (reg/f:DI 30 %r30)
                (const_int -296 [0xfffffffffffffed8])) [0 S8 A64])) -1 (nil)
    (nil))
/home/tausq/src/gcc-3.2/gcc/unwind.inc:132: internal compiler error: Internal compiler error in propagate_one_insn, at flow.c:1637
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [libgcc/./unwind-dw2.o] Error 1
make[2]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
make: *** [all-gcc] Error 2

The bootstrapping compiler is gcc-3.0.4

any ideas?
randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

             reply	other threads:[~2002-07-12  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12  7:27 Randolph Chung [this message]
2002-07-12 13:44 ` [parisc-linux] Problem building gcc-3.2 (cvs head) on hppa-linux John David Anglin
2002-07-12 13:44 ` John David Anglin
2002-07-12 16:56   ` Randolph Chung
2002-07-12 16:56   ` Randolph Chung
2002-07-12 17:52     ` John David Anglin
2002-07-12 17:52     ` John David Anglin
     [not found]       ` <20020712193842.GB8724@tausq.org>
2002-07-12 19:59         ` Randolph Chung
2002-07-12 19:59         ` Randolph Chung
2002-07-18 18:33 ` John David Anglin
2002-07-18 18:33 ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2002-07-12  7:27 Randolph Chung

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=20020712072703.GA8838@tausq.org \
    --to=randolph@tausq.org \
    --cc=gcc@gcc.gnu.org \
    --cc=parisc-linux@parisc-linux.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.