This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
VAX support in 2.95.2
- To: gcc at gcc dot gnu dot org
- Subject: VAX support in 2.95.2
- From: Chuck McManis <cmcmanis at mcmanis dot com>
- Date: Thu, 13 Jan 2000 01:52:13 -0800
Hello all,
Its quite humbling I've found to step aside from the SPARC or i386 world
and try to work with gcc :-) Case in point this evening is the VAX. I'm
running NetBSD 1.4.1 on a VAX and would like to build gcc 2.95.2 and a
fresh tool chain for it. (this is prepatory to building a full cross
compilation environment for the PDP-11 (its a longish story)).
The current gcc in NetBSD is egcs-2.91.60, and in the source tree I've
built it without error, however I thought as an exercise in getting to know
my way around I'd see if I could bring up 2.95.2. Its broken and I"m trying
to fix it, but I'm still on the learning curve.
This is what I've got:
1.) If I let configure guess what I'm building, it guesses
vax-unknown-nebsd1.4.1.
The configure actually seems to work better if I tell it vax-netbsd.
2.) When building makeinfo.c (doing a make bootstrap) I get an error:
../../../gcc-2.95.2/texinfo/makeinfo/makeinfo.c: In function `cm_today':
../../../gcc-2.95.2/texinfo/makeinfo/makeinfo.c:3988: warning: Delayed
evaluation of __builtin_constant_p not supported on this target.
../../../gcc-2.95.2/texinfo/makeinfo/makeinfo.c:3988: warning: Please
report this as a bug to egcs-bugs@cygnus.com.
Sounds like the MD files aren't correct, but I can't find any reference to
builtin_constant_p in any of the files to change it during the build.
3.) Gcc constantly complains that it doesn't understand "-J" (this shows
up in the
host overrides section of the gcc Makefile because it is in the x-vax
file in
gcc/config/vax why?)
4.) Is there an "owner" for the VAX ?
5.) I understand why the NetBSD folks build the tool chain with the bsd
makefiles
but I can't figure out if anyone is keeping the main gcc stuff up to date.
Anyway, its confusing and I'm looking for the place to start whacking. Some
(like the x-vax file) seem to be no-brainers, but the builtin_constant_p
stuff is still a mystery.
--Chuck