public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbglaw at lug-owl dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15491] ICE (Internal compiler error) while compiling glibc to vax-linux target
Date: Wed, 30 Jun 2004 07:57:00 -0000 [thread overview]
Message-ID: <20040630065333.16414.qmail@sourceware.org> (raw)
In-Reply-To: <20040517103549.15491.gabucino@mplayerhq.hu>
------- Additional Comments From jbglaw at lug-owl dot de 2004-06-30 06:53 -------
Subject: Re: ICE (Internal compiler error) while compiling glibc to vax-linux target
On Wed, 2004-06-30 02:36:05 -0000, danglin at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org>
wrote in message <20040630023605.3485.qmail@sourceware.org>:
> if gcc -DHAVE_CONFIG_H -I. -I../../gcc/libcpp -I. -I../../gcc/libcpp/../include
> -I../../gcc/libcpp -I../../gcc/libcpp/include -DLOCALEDIR="\"/usr/local/gcc/gcc
> -3.5.0/share/locale\"" -g -O2 -MT files.o -MD -MP -MF ".deps/files.Tpo" -c -o
> files.o ../../gcc/libcpp/files.c; \
> then mv -f ".deps/files.Tpo" ".deps/files.Po"; else rm -f ".deps/files.Tpo"; exi
> t 1; fi
> ../../gcc/libcpp/files.c: In function `read_file_guts':
> ../../gcc/libcpp/files.c:503: error: `ssize_t' undeclared (first use in this fun
> ction)
> ../../gcc/libcpp/files.c:503: error: (Each undeclared identifier is reported onl
> y once
> ../../gcc/libcpp/files.c:503: error: for each function it appears in.)
> ../../gcc/libcpp/files.c:503: error: parse error before "size"
> ../../gcc/libcpp/files.c:524: error: parse error before numeric constant
> ../../gcc/libcpp/files.c:524: error: parse error before numeric constant
> ../../gcc/libcpp/files.c:524: error: parse error before numeric constant
> ...
My build is still compiling, however, if you care enough, please go to
http://cvs.sourceforge.net/viewcvs.py/linux-vax/toolchain/experimental_toolchain/
and download the current version of experimental_toolchain.sh .
Then:
$ mkdir ~/some_temp_dir
$ cd ~/some_temp_dir
$ mkdir temp_for_build install
$ ..../experimental_toolahcin.sh --prepare --install --jbglaw ./temp_for_build/ ./install/
At least on my Linux system, that'll produce a vax-linux toolchain
(binutils + C-only gcc) and break somewhere in glibc some time later
(this is where I'm currently fixing:)
Oh, please read the comments inside the script; they'll provide some
important information (eg. you need to have some CVS pserver sources in
your ~/.cvspass).
MfG, JBG
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15491
next prev parent reply other threads:[~2004-06-30 6:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 20:15 [Bug c/15491] New: " gabucino at mplayerhq dot hu
2004-05-17 20:21 ` [Bug c/15491] " gabucino at mplayerhq dot hu
2004-05-17 20:43 ` gabucino at mplayerhq dot hu
2004-05-17 22:07 ` [Bug target/15491] " jbglaw at lug-owl dot de
2004-05-17 22:07 ` pinskia at gcc dot gnu dot org
2004-05-27 21:07 ` jbglaw at lug-owl dot de
2004-05-27 21:35 ` jbglaw at lug-owl dot de
2004-05-27 23:56 ` pinskia at gcc dot gnu dot org
2004-05-28 0:05 ` jbglaw at lug-owl dot de
2004-05-28 1:21 ` jbglaw at lug-owl dot de
2004-05-28 23:27 ` jbglaw at lug-owl dot de
2004-06-25 3:27 ` danglin at gcc dot gnu dot org
2004-06-26 15:24 ` jbglaw at lug-owl dot de
2004-06-29 3:03 ` pinskia at gcc dot gnu dot org
2004-06-30 2:50 ` danglin at gcc dot gnu dot org
2004-06-30 2:55 ` danglin at gcc dot gnu dot org
2004-06-30 6:22 ` jbglaw at lug-owl dot de
2004-06-30 6:25 ` jbglaw at lug-owl dot de
2004-06-30 6:48 ` jbglaw at lug-owl dot de
2004-06-30 7:57 ` jbglaw at lug-owl dot de [this message]
2005-01-09 15:45 ` danglin at gcc dot gnu dot org
2005-01-09 15:59 ` pinskia at gcc dot gnu dot org
2005-01-09 16:09 ` danglin at gcc dot gnu dot org
2005-03-25 17:31 ` cvs-commit at gcc dot gnu dot org
2005-03-25 17:55 ` cvs-commit at gcc dot gnu dot org
2005-03-25 18:31 ` cvs-commit at gcc dot gnu dot org
2005-03-25 19:28 ` danglin at gcc dot gnu dot org
2005-03-25 19:39 ` pinskia at gcc dot gnu dot org
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=20040630065333.16414.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).