🚀 go-pugleaf

Hello,
	I just built gcc-2.6.0 for my 3/80.  I read & reread the
INSTALL file, puzzled over config/m68k/sun*.h , Info files, &c. and
made the best judgment call I could about configuration options.
	I was then setting up to build bash (1.14.2 I think).  One of
the directions suggested a way to find out from one's compiler which
-Dmachine flags would need to be set in order to correctly build bash.
The result indicated that gcc was defaulting to generating 68020/68881
code, which was somewhat other than expected.  Below is the result of
gcc -v -E.

Reading specs from /home/mnt/lib/gcc-lib/sun3-sunos4.1.1/2.6.0/specs
gcc version 2.6.0
 /home/mnt/lib/gcc-lib/sun3-sunos4.1.1/2.6.0/cpp -lang-c -v -undef
-D__GNUC__=2 -D__GNUC_MINOR__=6 -Dmc68000 -Dsun -Dunix -D__mc68000__
-D__sun__ -D__unix__ -D__mc68000 -D__sun -D__unix -Asystem(unix)
-Asystem(bsd) -Acpu(m68k) -Amachine(m68k) -D__HAVE_68881__
-D__mc68020__ -Dmc68020 foo.c
GNU CPP version 2.6.0 (68k, MIT syntax)
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /home/mnt/sun3-sunos4.1.1/include
 /home/mnt/lib/gcc-lib/sun3-sunos4.1.1/2.6.0/include
 /usr/include
End of search list.
# 1 "foo.c"
main()  { }

I would appreciate advice on where in the build process to set the
default to generate 68030/68882 code (for the 3/80), and whether it is
preprocessor defines or Makefile variables or both.  Thanks in
advance.  Sorry about the long explanation.



			John R. Towler