At 02:05 PM 12/9/2003, John Klos wrote:
>Hi,
>
> > For what it's worth, I've made the changes needed so that you can do a
> > build with GCC 3.3.2.  Since GCC 3.3.2 doesn't have support for producing
> > PIC code, the system will built and linked entirely static.  This causes a
> > huge increase in program size.  As I expected, GCC 3.3.2 has major problems
> > generating valid VAX code.
> >
> > If you want, you can do a GCC3 build for VAX but you won't have working
> > programs.  To do this, you use these options with build.sh:
> >
> >       -V HAVE_GCC3=yes -V CHECKFLIST_FLAGS=-m
>
>This is very cool, but I'm a little confused about what you're saying. If
>we were to build an entire system which is completely statically linked,
>it wouldn't work, anyway? Or are you just saying that non-static stuff
>won't work?

I'm saying that GCC 3.3.2 emits bad VAX code.  (As does gcc-current).

Also, you should be using USE_TOOLS_TOOLCHAIN=no for a GCC3 build,
not HAVE_GCC3=yes.


-- 
Matt Thomas                     email: matt@3am-software.com
3am Software Foundry              www: http://3am-software.com/bio/matt/
Cupertino, CA              disclaimer: I avow all knowledge of this message.