Re: c++/4092: Use of ANSI features in gcc/cp/class.c

[Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>]

At 16:47 23.08.2001, Richard Lloyd wrote:
> > Before you continue to file bugs, read the build instructions, you are
> > supposed to do a 'make bootstrap', not a simple 'make' for a native build.
>
>You can't do this in HP-UX 11.00 ! It's another bug :-)

No, that's the main bug then.

>"make bootstrap" fails on HP-UX because the build system incorrectly
>attempts to link gcc-built .o files with HP's cc during the stage2 self
>re-build. This fails of course (__main not found), but just "make" (or
>"make install") works because it doesn't do the stage2 build.

You have to report this one.


>I think this is a generic problem on all platforms in fact, but only
>shows up on HP-UX because you can't link gcc-built .o's using the
>"cc" command (you have to link with the "gcc" command).
>
> From playing around with the gcc 3.X code, it's clear to me that the
>developers are sadly falling into the trap of almost always using
>a previous version of gcc to build a newer one. Before a release
>goes out, I feel that gcc should be built with at least one non-gcc
>ANSI C compiler and at least one K&R C compiler - it's obvious
>that this hasn't been done for any of the 3.X releases because
>ANSI C constructs are now creeping into the gcc 3.X code (particularly
>the gcc/cp tree), making it uncompilable on a K&R C compiler.
>Plus there's some constructs used that are baulked at by strict
>ANSI C compilers (which HP-UX 11.00's ANSI C is).

Only the code for the C compiler is K&R safe, because anything else is 
compiled by gcc itself in a correct bootstrap. As a workaround for now, 
first configure with --enable-languages=c and bootstrap the compiler, 
install it and bootstrap the full compiler with gcc then.

Franz.