From: Steve Thomas <sthomasgoo@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: building gcc-4.3.6 hangs on pex-common
Date: Sat, 07 Jan 2012 19:06:00 -0000 [thread overview]
Message-ID: <33099252.post@talk.nabble.com> (raw)
Hello,
I'm trying to compile/build gcc-4.3.6 on a linux Arm TS-7800 board (Linux
ts7800 2.6.34 #6 PREEMPT Mon Feb 21 16:37:33 CST 2011 armv5tel GNU/Linux).
Build seems to always hang on compiling pex-common.o, regardless of what I
try:
/home/swt/work/gcc/4.3.6/obj/./prev-gcc/xgcc
-B/home/swt/work/gcc/4.3.6/obj/./prev-gcc/
-B/home/swt/work/armv5tel-unknown-linux-gnueabi/bin/ -c -DHAVE_CONFIG_H -g
-O2 -I. -I/home/swt/work/gcc/4.3.6/gcc-4.3.6/libiberty/../include -W -Wall
-Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic
/home/swt/work/gcc/4.3.6/gcc-4.3.6/libiberty/pex-common.c -o pex-common.o
I've let this grind for days. The existing native gcc is 4.3.2. Anyone
have any pointers on how to get around this? I've been following all the
gcc config and build documents.
Thanks for you help!
-Steve
--
View this message in context: http://old.nabble.com/building-gcc-4.3.6-hangs-on-pex-common-tp33099252p33099252.html
Sent from the gcc - Help mailing list archive at Nabble.com.
reply other threads:[~2012-01-07 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=33099252.post@talk.nabble.com \
--to=sthomasgoo@gmail.com \
--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).