public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap Date: Sat, 17 May 2003 17:06:00 -0000 [thread overview] Message-ID: <20030517170600.11918.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/9631; it has been noted by GNATS. From: Randolph Chung <randolph@tausq.org> To: giovannibajo@libero.it, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, Dara Hazeghi <dhazeghi@yahoo.com> Cc: Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap Date: Sat, 17 May 2003 10:02:08 -0700 In reference to a message from giovannibajo@libero.it, dated May 17: > Synopsis: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap > > State-Changed-From-To: open->feedback > State-Changed-By: bajo > State-Changed-When: Sat May 17 06:57:31 2003 > State-Changed-Why: > See Dara's question. Same thing with gcc-3.3 release: /home/tausq/build/build-3.3/gcc/xgcc -B/home/tausq/build/build-3.3/gcc/ -B/opt/palinux/hppa64-linux/bin/ -B/opt/palinux/hppa64-linux/lib/ -isystem /opt/palinux/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../../gcc-3.3/gcc -I../../gcc-3.3/gcc/. -I../../gcc-3.3/gcc/config -I../../gcc-3.3/gcc/../include -fexceptions -c ../../gc c-3.3/gcc/unwind-sjlj.c -o libgcc/./unwind-sjlj.o ../../gcc-3.3/gcc/unwind-sjlj.c:56: error: size of array `data' is too large randolph -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/
next reply other threads:[~2003-05-17 17:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-17 17:06 Randolph Chung [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 9:14 ehrhardt 2003-05-19 1:26 Randolph Chung 2003-05-19 0:06 Giovanni Bajo 2003-05-17 6:58 giovannibajo 2003-05-17 1:46 Dara Hazeghi
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=20030517170600.11918.qmail@sources.redhat.com \ --to=randolph@tausq.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).