freebsd_amp_hwpstate/gnu/usr.bin/cc/Makefile

#
# $Id$
#

SUBDIR= cc_tools cc_int cpp cc1 cc cc1obj cc1plus c++ f77 libgcc doc

.include <bsd.subdir.mk>
Here comes the right import of gcc-2.6.0. 1994-08-02 20:15:59 +00:00			`#`
Man the lifeboats! Tie down the hatches! Red alert! Activate gcc-2.7.2.1! (the old cc has been tagged with "gcc_2_6_3_final" so we have a reference point in case of unforseen disasters...) This has the objc backend active, and I think I've managed to get the f77 f2c support through in one piece, but I don't know fortran to test it. A 'make world' change and libobjc commit will follow. If you normally do 'make -DNOCLEAN world', do not do so this time, I know it can fail with groff. This version of gcc makes a LOT more warnings on our kernel. 1996-09-19 15:53:53 +00:00			`# $Id$`
Here comes the right import of gcc-2.6.0. 1994-08-02 20:15:59 +00:00			`#`

Man the lifeboats! Tie down the hatches! Red alert! Activate gcc-2.7.2.1! (the old cc has been tagged with "gcc_2_6_3_final" so we have a reference point in case of unforseen disasters...) This has the objc backend active, and I think I've managed to get the f77 f2c support through in one piece, but I don't know fortran to test it. A 'make world' change and libobjc commit will follow. If you normally do 'make -DNOCLEAN world', do not do so this time, I know it can fail with groff. This version of gcc makes a LOT more warnings on our kernel. 1996-09-19 15:53:53 +00:00			`SUBDIR= cc_tools cc_int cpp cc1 cc cc1obj cc1plus c++ f77 libgcc doc`
Here comes the right import of gcc-2.6.0. 1994-08-02 20:15:59 +00:00
			`.include <bsd.subdir.mk>`