From: squirrel@_HOSTNAME_.headnut.org
To: gcc-help@gcc.gnu.org
Subject: problem bootstrapping gcc 3.4.1
Date: Sun, 22 Aug 2004 05:12:00 -0000 [thread overview]
Message-ID: <20040821192808.GA7150@ivanova.headnut.org> (raw)
hey,
i'm trying to bootstrap gcc 3.4.1 with uclibc for an embedded
device toolchain, but i keep getting errors upon the compile.
the relevant lines:
$ tar xfj gcc-3.4.1.tar.gz
$ mkdir build-boot-gcc
$ cd build-boot-gcc
$ ../gcc-3.4.1/configure --target=i386-linux \
--prefix=/home/squirrel/projects/stb_pbx/toolchain \
--without-headers \
--with-newlib \
--disable-nls \
--enable-languages=c
$ make all-gcc
/home/squirrel/projects/stb_pbx/build-tools/build-boot-gcc/gcc/xgcc
-B/home/squirrel/projects/stb_pbx/build-tools/build-boot-gcc/gcc/
-B/home/squirrel/projects/stb_pbx/tools/i386-linux/bin/
-B/home/squirrel/projects/stb_pbx/tools/i386-linux
/lib/
-isystem /home/squirrel/projects/stb_pbx/tools/i386-linux/include
-isystem /home/squirrel/projects/stb_pbx/tools/i386-linux/sys-include
-O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc-3.4.1/gcc
-I../../gcc-3.4.1/gcc/. -I../../gcc-3.4.1/gcc/../include -DL_muldi3
-c ../../gcc-3.4.1/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from ./tm.h:11,
from ../../gcc-3.4.1/gcc/libgcc2.c:43:
../../gcc-3.4.1/gcc/config/i386/linux.h:217:20: signal.h: No such
file or directory
../../gcc-3.4.1/gcc/config/i386/linux.h:218:26: sys/ucontext.h: No
such file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
any help on fixing this issue is greatly appreciated! please
e-mail directly or cc me in the reply as i am not on the gcc-help
list.
thank you!
chris
reply other threads:[~2004-08-21 19:28 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=20040821192808.GA7150@ivanova.headnut.org \
--to=squirrel@_hostname_.headnut.org \
--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).