[Bug target/15491] ICE (Internal compiler error) while compiling glibc to vax-linux target

["jbglaw at lug-owl dot de" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From jbglaw at lug-owl dot de  2004-06-30 06:22 -------
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>:
> you will see that interest in this target isn't totally dead.  There has
> been a fair bit of work done on binutils for the netbsd and linux targets.
> Clearly, this was done with the assumption that the VAX target wouldn't
> be removed from GCC.  However, I'm going to stay out of the debate regarding

Quite right!

> 1) It's much lower priority than hppa and my time is limited.
> 2) The VAX that I have has a rather limited amount of memory and runs
>    ultrix (until recently, this machine was used for remote data access
>    from two scientific monitors and there wasn't the time or money available
>    to upgrade the software used for this activity).  While the machine
>    could be switched over to a newer OS, it would still be hobbled by
>    its limited memory.  Hopefully, one of the people interested in netbsd
>    or linux will take it over, although I know they fear the learning
>    curve.

Do you already know Linux or *BSD? ...and how much memory is installed
in your box?

Booting a VAX with Linux isn't all that hard. Depending on the model,
there may or may not be a SCSI driver available, but network interfaces
are supported. So at least, you can MOP boot and run into NFS-root.

> With the mainline, C would build after Jan's patch to fix a case falls
> though problem until late January.  Then, another change broke this
> again.  At the moment, there are new issues such as:

Hu? I've done builds after January for sure:)

> 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
> ...

I'll start another build right now to check your claim. How did you
configure gcc and binutils? On what machine are you building on?

MfG, JBG



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15491